What's New in Version 15.8.00 to 15.8.11
Version 15.8.11
Enhancements
Payroll
76827
The New Zealand Government handed down its Budget on 30 May 2024, confirming the promised changes to the tax thresholds for personal income tax.
The new Tax thresholds to apply from 31 July 2024 are being updated via the Welcome Page Legislative Update Button feature, providing each customer with control over the timing of this update.
The change to the tax thresholds however also requires an update to the description of some Tax Codes used for Supplementary Income in Preceda.
The below Tax Code descriptions have been updated to reflect the new thresholds:
Tax Code | Current Description | New Description |
---|---|---|
P | SB - Secondary Income <=$14,000 | SB - Secondary Income <=$15,600 |
S | SB - Secondary Income $14,001-$48,000 | SB - Secondary Income $15,601-$53,500 |
U | SH - Secondary Income $48,001-$70,000 | SH - Secondary Income $53,501-$78,100 |
V | ST - Secondary Income $70,001-$180,000 | ST - Secondary Income $78,001-$180,000 |
Transition to Dayforce
75842
To support Preceda customers in their transition to Dayforce, a new Extractor view has been created for Employee KiwiSaver Data. This Extractor view includes details from the KiwiSaver fields on the Tax Information screen, as well as current employee and employer KiwiSaver contribution rates from the Allow/Deduct screen, all in the format required by Dayforce Activate. The employee selection will be based on the Payrun Group(s) selected on the Dayforce Configuration screen.
76150
A new Dayforce Extractor view has been created for Confidential Identification, enabling the option for employee's Passport, Visa and Lic/Reg details to be transitioned to Dayforce via Activate. The employee selection will be based on the Payrun Group(s) selected on the Dayforce Configuration screen.
Passport Details & Visa Details
These screens in Preceda are designed specifically for recording only Passport & Visa information, so all existng records from the selected employees will be included in the Extractor results.
Lic/Reg Summary
This screen is more flexible in design, and we can see that it has been used by many customers for a wide variety of reasons. We understand that only some of this data may be of interest in Dayforce, so a new "Extract" field has been added to the Lic/Reg Codes screen, which will be used to filter the employee Lic/Reg Summary records to includse in the Extractor results. By default, all Lic/Reg Codes will have the new "Extract" field unticked, so this will need to be updated against any Lic/Reg Codes that are required to be included in the upload to Dayforce.
75663, 76814
During the Getting Started stage of a Dayforce Activate project, customers are provided with an option to include/exclude loading historical compensation and job history data for their employees.
To support customers who opt to include this historical data, two new Dayforce Extractor views have been created, and the existing Dayforce Extractor views for Employee Data and Fresh Start Employee Data have been updated to include additional information.
Job History
The new Job History Data view in Extractor will generate output by referencing prior effective dates records on the Position screen excluding the current record. The employee selection will be based on the Payrun Group(s) selected on the Dayforce Configuration screen.
A required field in Dayforce is the Reason for the historical job change. By default, where a Change Reason is found against the employee record in Preceda the description from this will be output, and where no Change Reason is found the output for this field will be sourced from a new Preceda Variable *DF_HISTORY_REASON. As this would require configuration of all the existing Preceda Change Reason descriptions in Dayforce - which may not be desirable - we have introduced a new Program Control option using position 17 of DAYFC which can be updated to blank or N to have all records populate the Reason field with the value sourced from *DF_HISTORY_REASON.
Compensation History
The new Compensation History Data view in Extractor will generate output by referencing prior effective dates records on the Salary / Salary Code screens, excluding the current record. The employee selection will be based on the Payrun Group(s) selected on the Dayforce Configuration screen.
A required field in Dayforce is the Reason for the historical compensation change. By default, where a Change Reason is found against the employee record in Preceda the description from this will be output, and where no Change Reason is found the output for this field will be sourced from a new Preceda Variable *DF_COMP_HIST_REASON. As this would require configuration of all the existing Preceda Change Reason descriptions in Dayforce - which may not be desirable - we have introduced a new Program Control option using position 17 of DAYFC which can be updated to blank or N to have all records populate the Reason field with the value sourced from *DF_COMP_HIST_REASON.
Employee Data
This existing Dayforce Extractor view includes some optional date fields which have not been populated with any values, however these dates are required to enable loading of historical data via Activate. The output for this extract has now been updated to include this additional information:
-
Job Start Date = Effective Start date of employee's current Position.
-
Status Start Date = Effective Start date of employee's current Salary.
Fresh Start Employee Data
This existing Dayforce Extractor view includes some optional date & change reason fields which have not been populated with any values, however this data is required to enable loading of historical data via Activate. The output for this extract has now been updated to include this additional information:
-
Job Start Date = Effective Start date of employee's current Position
-
Job Reason Code = Value from Preceda Variable *DF_HISTORY_REASON
-
Status Start Date = Effective Start date of employee's current Salary
-
Status Reason Code = Value from Preceda Variable *DF_COMP_HIST_REASON
76561
The following updates have been implemented to the System Health Check screen to improve usability of this Dayforce Readiness feature for customers and Services consultants working with a Preceda database, to prepare it for onboarding data into the customer's Dayforce instance using the Dayforce Activate tool:
-
Additional checks on Locations and Country Codes
-
New check for Emergency Contacts with no Relationship
-
New checks for Passport Details and Lic/Reg Summary records with missing Issue Dates or Country
-
New checks for NZ employee KiwiSaver details
-
New check for employees with no Manager / Reports To
-
Update to existing checks to include historical versions of employees with current financial year data
76621
To reduce the time for Implementation Consultants working with a customer in transition from Preceda to Dayforce, some Extractor reports have been introduced to all AU and NZ databases, based on the new Extractor views introduced in this release. The Dayforce Report Manager packages for Additional Information have also been updated to include these new Extractor reports.
This provides Consultants with quick and easy access to running these Data Load extracts when required, with the generated files formatted and named ready for Dayforce Activate to consume. The updated Report Manager packages are now complete with all employee data load files available in Activate's new Preceda Centralized Data Load wizard.
Please note that these reports & packages are only available once the Dayforce Transition Setup Utility has been run by the Preceda Application Services team. If you have any questions in relation to gaining access to these reports & packages, please contact your Customer Success Manager.
New Extractor Reports
Extractor Reports have been introduced to all AU and NZ databases for each of the below listed Dayforce Data Loads Extractor views:
-
Additional Employee Data
-
Confidential Information Data
-
Job History Data
-
Compensation History Data
-
Employee KiwiSaver Data (NZ only)
As with other Extractor Reports deployed across multiple customers, the Owner & Modified By information for these reports is set to 'SYSTEM'.
These Extractor Reports are all configured with "Output To" set to 'Export', and the "File Type" set to 'Comma Separated Values (*.csv)'.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Payroll
76714
Where an employee had a standard recurring Allow/Deduct record for an After Tax Deduction (Classification 4) with a deduction Priority set, and the Standard Amount was a negative value, this value was being doubled causing the employee's Net value to be Out of Balance. This has now been corrected.
76710
An issue was encountered by one customer where a required record in the PAYRDAT file was missing when the Payrun Header was created, leading to some problems with the results of the payrun. Protective measures have now been introduced to ensure that new Payrun Header records will not be successfully saved without this required PAYRDAT record.
66289
An issue was reported for a scenario where Retro was run overpay periods where previous Retros had been generated which included Salary Code overrides. The Salary Code override applied in the first Retro was not being considered in the second Retro causing incorrect results. This has now been corrected.
Version 15.8.10
Enhancements
Payroll
60283
The Australian financial / tax year starts from 1 July and runs through to 30 June of the following year and it is common each year for there to be updates that need to be applied from 1 July for the new financial year to various indexed figures and tax withheld schedules.
For 2024-2025, most of the updates will be applied by an automated feature via the Tax Table Update Button on the Welcome Page of Preceda, while some updates will need to be applied manually by the customer.
The Tax Table Update Button will be available from Friday, 21 June 2024. Note that the Administrator and Security Officer must be set to Y, via the Define Users screen, for the User Profile(s) who will need to have this action available.
The updates to the Tax Table and Superannuation starting on July 1, 2024, are as follows:
-
Tax Table updates for the Government's Stage 3 tax cuts, delivering tax relief to individual taxpayers
-
The ETP Thresholds Cap increases to $245,000. There is no change to Whole of Income cap, and this remains at $180,000 as it is a non-indexed figure.
-
The death benefit termination payment ETP cap increases to $245,000.
-
The Lump Sum D / Redundancy Threshold increases to $12,524 plus $6,264 for each completed year of service.
-
SGC / Superannuation Percentage increases to 11.5%. The superannuation guarantee legislation has already been set for super payments to increase 0.5% each year until reaching 12% in 2025.
-
SGC Maximum Contributions Base (MCB) increases to $65,070 per quarter.
-
The Concessional Super Cap increases to $30,000, however this cap is not managed by payroll. This is an employee responsibility.
Please note that updates to Superannuation are not included in the automated feature via the Welcome Page's Tax Table Update Button. These updates will need to be handled manually. Please see below for links to Community Articles covering the steps required to perform this update:
76648
From 1 July 2024, through their Back Pocket Boost plan, the Nationals have a goal of delivering meaningful tax reductions to provide cost of living relief to New Zealanders, who have seen no change in personal income tax rates and thresholds since 2010.
The Nationals have proposed the following adjustments to tax thresholds:
Existing Threshold | Proposed Threshold | Threshold Rate |
---|---|---|
$14,000 | $15,000 | 17.50% |
$48,000 | $53,500 | 30% |
$70,000 | $78,100 | 33% |
Note: The $180,000 income tax threshold will remain in place. The Nationals have ruled out removing the 39% top tax rate in their first term due to fiscal and economic pressures. However, higher-income earners will benefit from their plan as they, like other taxpayers, will pay less tax on their earnings under $78,100.
National also propose to increase eligibility for the Independent Earner Tax Credit (IETC) to compensate for the impact of inflation, by extending the upper limit of eligibility from $48,000 to $70,000, with abatement of the payment starting from $66,000. The lower limit of IETC eligibility will remain the same at $24,000.
Dayforce have prepared for this proposed update to the Tax Tables, and once confirmed following the May Budget we will provide Preceda users with the ability to control the timing of the updates they will need to apply from July 1, 2024. This will be handled by enabling the standard Welcome Page Legislative Update Button feature towards the end of June 2024.
Once this feature is enabled:
-
Users who have "Security Officer" set to Y will see the message on the Welcome Page.
-
Only Users who also have "Administrator" set to Y will be able to click the button
When the button is clicked, the following updates will be actioned:
-
Update Tax Tables with new thresholds.
-
Update Preceda Variable *PP_TAXTABLEUPD with details of date, time and User who clicked the button
The message and button will then stop being displayed on the Welcome Page.
Note that the current financial year reference stored in Preceda Variable *PP_TAXYEAR will not be updated as part of this action.
A Community Article will be published with more details, once the planned adjustments to tax thresholds are confirmed.
Transition to Dayforce
76565
The Tax Information NZ template has been updated in Dayforce Activate to include fields for the employee’s ESCT (Employer Superannuation Contributions Tax) information, which is available in Preceda on the YTD Gross, Tax & Net window.
For this update, the following are implemented:
-
The existing Dayforce Data Load Extractor view now includes three (3) new fields:
-
ESCT Rate - this is sourced from the YTD gross, Tax & Net field ESCT Tax Rate multiplied by 100. If there is no value in this field, the default value will be "System Calculated".
-
ESCT Effective Start Date - this refers to the Start Date of current financial year.
-
ESCT Effective End Date - this refers to the End Date of current financial year.
-
-
The existing Extractor Report has been to be updated to include the 3 new fields.
76140
To reduce the time for Implementation Consultants working with a customer in transition from Preceda to Dayforce, some Extractor Reports have been introduced to all AU and NZ databases, based on the new Extractor views. This will provide Consultants with quick and easy access to running these Data Load & Parallel Run extracts when required, with the generated files formatted and named ready for Dayforce Activate to consume.
Please note that these reports will only be available once the Dayforce Transition Setup Utility has been run by the Preceda Application Services team. If you have any questions in relation to gaining access to these reports, please contact your Customer Success Manager.
New Extractor Reports for Go-Live
New Extractor Reports have been introduced to all AU and NZ databases for each of the below listed Dayforce Data Loads Extractor views
-
Earning Election Data
-
Deduction Election Data
-
Earning YTD Data
-
Deduction YTD Data
-
Tax YTD Data
-
Time Away from Work Data
Each of the above Extractor Reports will simply contain all fields from the relevant view. As with other Extractor Reports deployed across multiple customers, the Owner & Modified By information for these reports is set to 'SYSTEM'. These Extractor Reports are all configured with "Output To" set to 'Export', and the "File Type" set to ‘Comma Separated Values (*.csv)'.
New Extractor Reports for Parallel Run
A new Extractor Report has been introduced to all AU & NZ databases, which includes all the views related to Legacy payroll data. The main report is based on the Legacy Company Totals view, and includes a runtime prompt on the Payrun Header ID field for easy selection of the historical Preceda payrun used in the parallel payrun testing in Dayforce.
A sub-report has been added for each of the below listed Dayforce Data Loads Extractor views:
-
Legacy Employee Earning
-
Legacy Employee Deduction
-
Legacy Employee Net Pay
-
Legacy Employee Tax
-
Quick Entry Import
-
These sub-reports are all linked to the Legacy Company Totals main report using the Payrun Header ID field.
-
Display of the Payrun Header ID field in the main report, and all sub reports is hidden, to ensure that this information is not included in the results.
-
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Framework
76727
The issue encountered when adding a Variable in the Notification Text Drilldown of the Alert Setup screen has now been fixed. The Variable will now be successfully added and Preceda will not be forced to close.
Payroll
75499
The SGC calculations for employees under 18 on a fortnightly payrun have been now corrected.
Where the costing dates are being checked to identify the separate weeks within a fortnight - Program Control PAY29, position 23 = Y - the earnings from the prior period (dated in same month as current period end & super payment date) are all assessed as earnings within the same month; even when the costing date on the transactions is within the previous month.
Where the total hours for the fortnight are divided by two - Program Control PAY29, position 23 is not Y - the hours from both fortnights within the month will be correctly assessed to ensure employees will not be paid Super on weeks with less than 30 hours; even when both payruns have the same Super Payment Date.
73996
Lump Sum E will now update accordingly with no errors display if within the Financial Year is within the last 10 years. At the same time, Lump Sum E updates will produce an error accordingly when a previous Financial Year value exceeds 10 years prior to the current year.
75674
When an employee is terminated via Express pay Termination Wizard, at the time the payment is released and processed, the employee's effective dated Superannuation records - along with all other standard allow/deduct records - are ended on the Termination date.
After the Express payment is passed to payroll, if the employee's Termination date is prior to the period start date of the payrun, as the Recipient and Reference details for the Superannuation Funds are no longer current within the date range of the payrun they are not recorded against the Super payment. This detail is therefore missing in the Super Stream History file and is not populated in the SAFF leading to rejections from Super clearing houses.
This has now been corrected to ensure that if there is no Effective Dated record for the Super A/D within the current pay period, that we look for the Effective Dated A/D information as at the employee's Termination Date.
Version 15.8.09
Enhancements
Framework
76562
Recent global changes to the log-on procedure for Preceda included security updates that prevented users from logging on to Preceda multiple times, using a single browser. As a result, customers experienced delays and other interruptions to typical business functions.
We are pleased to confirm you will again have access to multiple Preceda sessions/tabs in the same browser, at the same time.
Note that the recent security update to strengthen our defenses against malicious cyber-attacks, has not been compromised by the re-enablement of multiple Preceda sessions.
Transition to Dayforce
76198
To support the transition of Preceda customers to Dayforce, a new field, Dayforce Description, has been added to both the Allow/Deduct Codes and Hours Type Codes screens. The new Dayforce Description field is a non-mandatory free-text field that will allow customers to enter the Earning & Deduction descriptions they will be using in Dayforce when data relating to these codes is transitioned from Preceda.
The new field has also been added to the Mapper and Extractor Views of each corresponding screen.
76139, 76371
To assist with Parallel Run testing between Preceda and Dayforce, the Activate tool includes a feature to compare the payrun results from a Legacy payroll application, with the results calculated from the customer’s new Dayforce instance.
To support this feature, some Extractor views have been designed to output Parallel Run Legacy Data from Preceda in the format required by the templates available in Dayforce Activate. These new views include a prompt field to select the required historical payrun in Preceda, which the Parallel Run in Dayforce is being performed for.
Below are the Legacy Data Extractor views that were added:
-
Legacy Employee Deduction
The main source of information for this Extractor view are the Deduction records from the Timecard Cost History (TCOSTH) file, with totals calculated for each employee & Deduction/Legacy Code combination.
-
Legacy Employee Earning
The main source of information for this Extractor view are the Hours/Allowance records from the Timecard Cost History (TCOSTH) file, with totals calculated for each employee & Earning/Legacy Code combination.
-
Legacy Employee Net Pay
The main source of information for this Extractor view are the Net Pay amounts from the Timecard Cost History (TCOSTH) file, with totals calculated for each employee & Legal Entity/Company combination.
-
Legacy Employee Tax
The main source of information for this Extractor view are the Tax and Gross amounts from the Timecard Cost History (TCOSTH) file, with Tax and Gross totals calculated for each employee paid in the specific historical payrun.
The following notes apply to all the Extractor views mentioned above:
-
These Extractor views are only available when Preceda Variable for *PP_DFI_STATUS = 'A' or 'M'.
-
The Payrun Group(s) selected as an Integration Candidate on the Dayforce Configuration screen will not be referenced for these Extractor views, as it should only be run for a single Payrun Group at any time, and this is controlled by the Payrun Environment that the user is currently active in.
-
A prompt is provided on these Extracts for selection of the historical payrun to be included in the output, as this data is then to be imported into Dayforce Activate for comparison with the results from the parallel payrun executed in Dayforce.
-
Display of the Payrun Header ID field used to select the required historical payrun will need to be unchecked for Display in the associated Extractor reports before they are run to ensure this field is not output to the CSV files uploaded in Dayforce Activate.
76373
To assist with Parallel Run testing between Preceda and Dayforce, the data entry records which were included in the historical payrun(s) processed in Preceda, need to be extracted and imported into the Quick Entry screen in Dayforce. As Parallel Run testing is usually performed after the original payrun(s) in Preceda have been closed, this information will be obtained from the Timecard Cost History file, with the ability to select which historical payrun the data is to be sourced from.
For this, a new Extractor view, Quick Entry Import, has been introduced. This Extractor view is aligned with the Dayforce import available via the Quick Entry tab in a loaded Payrun. Note that this is not a template available within Activate, and the data is imported directly into the customer's Dayforce instance. The main source of information for this Extractor view comes from the Timecard Cost History (TCOSTH) file, only outputting Hours and A/D records with a Source of Change indicating that the data originated from Entry via Single Screen or Prepay/Rebank Entry.
The following notes also apply to this extractor:
-
These extractor views are only available when Preceda Variable for *PP_DFI_STATUS = 'A' or 'M'.
-
The Payrun Group(s) selected as an Integration Candidate on the Dayforce Configuration screen will not be referenced for these Extractor views, as it should only be run for a single Payrun Group at any time, and this is controlled by the Payrun Environment that the user is currently active in.
-
A prompt is provided on these Extracts for selection of the historical payrun to be included in the output.
-
Display of the Payrun Header ID field used to select the required historical payrun will need to be unchecked for Display in the associated Extractor reports before they are run to ensure this field is not output to the CSV files uploaded in Dayforce Activate.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Payroll
76093
The Time Card Entry Report (TCPPRB) will now correctly display all details of the records for Allow/Deduct Codes for Prepayments/Rebank transactions.
75238
When creating an Amendment via the drill-down on STP Summary History records, and data has been populated in the Lump Sum E browse-list, validation needs to check the value of the Financial Year against the records in the browse-list to ensure that they are within 10 years of the Financial Year of the STP Summary History record. Thus, following this rule, the creation of an Amendment which includes Lump Sum E records over 7 years old should be a valid transaction.
The validation check to ensure that records are within 10 years of the Financial Year of the STP Summary of the STP Summary History record when creating Amendments with Lump Sum E records has now been fixed. Amendments will now be created as expected with no error encountered.
Time
76642
When a terminated employee with Time Details information was reinstated, their status in Preceda Time was not being updated back to Active (A). This resulted in a search performed on the Time Editor screen not displaying the reinstated employee. This has been corrected to ensure the employee's status in Preceda Time is updated correctly during the reinstate process.
Version 15.8.08
Enhancements
Administration
75172
As part of the Average Hours updates initially delivered via PREC-73703, a new option has been introduced in the History Retention screen for Average Hours Summary History. This option enables you to purge Average Hours Summary records based on selected criteria.
Furthermore, the warning message displayed in the Purge History screen has been updated to reflect Average Hours Summary History component.
Framework
75728
Ceridian HCM Holding Inc. has transitioned the company's brand to Dayforce effective last January 2024.
In line with this brand transition to Dayforce, Preceda required updates to replace the Ceridian branding particularly with the logo used on the logon page and within the product, as well as the copyright.
Integration
75785
For customers choosing Dayforce as their new HCM solution, there is a possibility that multiple, but not all, Payrun Groups will be included in the initial onboarding. Hence, we have now provided an ability for viewing the Dayforce Readiness Health Check items for multiple Payrun Groups, which will be based on the selection in the Dayforce Configuration screen.
The following updates were implemented to the System Health Check screen to improve usability of this feature for customers and Services consultants working with a Preceda database, to prepare it for onboarding data into the customer’s Dayforce instance using the Dayforce Activate tool:
-
Update to Blank Environment display of Dayforce Readiness Results
The employee related information displayed on the System Health Check screen is specific to the Payrun Environment that the user is currently active in. The results within a Payrun Environment are only relevant to the Payrun Group connected to that Environment. When in the "Blank" Payrun Environment, the System Health Check results display information for all employees from all Payrun Groups.
For some large customers, there is a potential that the onboarding to Dayforce will be done in stages. This could include the onboarding of multiple Payrun Groups, but not all of them. To assist the customer/Services consultant to manage this scenario, the logic for the Dayforce Readiness section when the user is in the "Blank" Payrun Environment has been updated. The employee related checks in this section will now include all employees who belong to the Payrun Groups that have been selected as an "Integration Candidate" via the Dayforce Configuration screen.
Please note that the behaviour within a Payrun Environment should continue to work as it does today. This should not be based on the Dayforce Configuration settings, but still display results for employees who belong to the Payrun Group connected to that Environment; even when this Payrun Group is not selected on the Dayforce Configuration screen.
-
Exclude Dayforce Readiness Items from Overall Health Percentage (%)
The errors displayed in the Dayforce Readiness section of the System Health Check will no longer be included in the overall totals seen at the top of the screen, as well as to the overall total displayed on the Payrun Dashboard screen.
As these Health Checks are specific to the requirements for cleansing customer data in preparation for migrating to Dayforce, they have no impact on the health of Preceda's payrun processing or legislative reporting.
Please note that the Dayforce Readiness section will be visible for customers who have chosen Dayforce as their new HCM solution, where Position 2 of Preceda Variable *PP_DFI_STATUS = 'Y'.
Payroll
63921
The New Zealand Year End process to Update ESCT Rates for employees for the new financial year performs calculation to determine if the income, kiwi-saver, and superannuation values in earnings history cover the full previous financial year and can be reported as Actual values. If the earnings history information in Preceda was not determined to be exactly one year, an estimation was calculated with the results reported as Estimated values.
This raised issues as sometimes due to additional off-cycle Payruns, an employee could have more than 52 tax weeks or 12 tax months, which should not be considered as Estimated but is considering it as is.
To improve and provide a more accurate calculation, the NZ Year End process has been updated with the following conditions:
-
If Total Tax Weeks/ 4.3333 is greater than or equal to 12 (months) then it will be considered as ACTUAL income, where the values are totaled from all earnings in the last financial year.
-
If Total Tax Weeks/ 4.3333 less than 12 (months) then it will be considered as ESTIMATED, where the values are calculated estimates of their earnings based on IRD guidelines.
69911
When managing legally enforceable payroll deductions such as child support or court attachment orders, there is a requirement to limit the amount that can be deducted from an employee to protect a set amount of their net earnings.
Previously in the New Zealand Preceda functionality, the assessment for Protected Net was limited to the deductions defined as child support, which has a specific Allow/Deduct setup. With this enhancement, the functionality has been extended to support court attachment orders or garnishees, which need to be considered under the Protected Earnings.
This enhancement offers two alternative options for setting the Protected Net for court attachment orders which are: the employee specific Protected Net (Weekly) amount or the default 60% Protected Net used for Child Support deductions. If an employee has a court order specifying a particular Protected Net Amount, it's recommended to utilize the Protected Net (Weekly) amount, which can be configured in the Salary screen. Alternatively, if an employee doesn't have a specified Protected Net amount from the court order, the default % of Protected Net used for Child Support will be used. This is defined in the Dependent Rebates screen.
A new field "Use with PEA" has been introduced on Allow/Deduct Code screen for New Zealand. When this field is selected, Preceda recognises that this deduction code is intended for court attachment order and the employee's protected net/earnings need to be checked before processing this deduction. By default, this field is read-only and becomes editable only when all the following conditions are met:
-
The selected Classification is either: 4, 8, P, or R
-
The Deduction Priority is set to 1
-
The Allow Partial Deductions is set to Yes.
With this enhancement, the Payrun Process has been updated to incorporate Protected Net validation for court attachment orders/garnishees. When Allow/Deduct Codes are configured with the Use with PEA field enabled, the following rule will be applied to determine the Protected Net amount:
-
If a valid effective dated Protected Earnings (weekly) amount is available via Salary > Protected Net (Weekly) field, system uses this value as the protected net for attachment orders.
-
If Protected Earnings (weekly) amount is not available (Protected Earnings Weekly value is zero), system will apply default IRD 60% of protected net via Dependent Rebate > Protected Net for Child Support.
Deduction Order
The system assigns the highest deduction priority to child support deductions. Once child support deductions are processed, system then prioritises court attachment orders for deduction based on the Deduction Priority on the A/D code.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
73320
A validation has now been added for Employee ID for Compliance Details (Mapper M001101) so that an error will occur when creating new Compliance Details for employee ID that does not exist in the system. Mapper will now correctly reject records with an invalid employee ID.
76159
The Effective Date field in the Maintenance History file will now update consistently for all records, when changes are made to the relevant employee fields.
58368
The number of weeks per year of service on the Termination Pay screen, used for configuring the rules for a Redundancy or Notice in Lieu of Termination payment, accepted values with up to 2 decimal place, allowing for part weeks (i.e., 3.25 weeks). Once the number of weeks to pay based on the years of service was calculated only whole weeks were being paid, which provided an incorrect result if the total weeks to pay included a part week. This has now been resolved to ensure the correct number of weeks is paid.
72425
Updates to employee information in the Administration module was being synced with the employee's Time Records, regardless of the status of the employee record in the Administration module. Time Records will now be syncing only on the updates made to the employee's Active version (A) status and not on the updates made to historical versions, e.g. Reinstated (R).
Framework
61777
Preceda will now use updated HTTP Headers to enhance the security of the web page and help detect and mitigate certain types of attacks.
Payroll
56274
When pay slips have been configured to show Costing Dates for an Allowance/Deduction, there was an issue when multiple records existed for the same A/D code, where the pay slip displayed only 1 record and date with the total from all records.
Costing Date for Allow/Deductions will now correctly display on Pay slips accordingly based on the conditions applied in Program Control A440 Position 45.
74628
All the descriptions of each level from Level 1-5 now display correctly and accordingly on the Costed Reconciliation Report (PRP522PRT).
60191
The Direct Credit Create Report (PAY64PRT) has been updated to display headers on all pages so customers will be able to identify which Costing levels the totals page belong to.
57498
The correct costing levels are now picked up and applied correctly in the Payrun Journal and Reconciliation report when a prepayment is processed for an employee who has a pay frequency not selected on the Payrun Header. Thus, these payrun reports will now display all employees under their respective company, as expected.
62891
If an auto-paid employee's YTD Gross plus their Gross from current pay was within $1.00 of their Annual Salary, Preceda was doing an adjustment to the employees pay to make it equal the Annual Salary. This resulted in an incorrect payment for an employee who reached this YTD amount during the financial year, prior to the final payrun of the year. This has now been updated to ensure this adjustment is no longer performed.
73376
Unused Leave Cash Out will now generate the expected payment using the correct Pay Rate whether the generated Hours Code has Compare Results With field populated or not.
69930
The following T&A Processes has been corrected to ensure that they will no longer affect or update the Integration Lock Status:
-
T/A Import
-
T&A Edit
-
Clear T&A Import
-
Merge T&A Import
-
Remove T&A from Time Entry
76074
The JP Morgan NZ format has now been corrected so that records output from a Deductions via Bank EFT configured A/D Code are populated with all the required field information. Bank EFT file will now display the record for the A/D Codes with correct Bank Details as expected.
75754
The Lump Sum E will now report correctly via STP if multiple values exist for the same Financial Year.
71339
Superannuation was not calculating on some termination wizard payments when they had been released and passed to Entry via Single Screen. SGC will now be processed and generated for terminated employees whether their termination payment status is set to "Released" or "Release and pass to Time Card", as expected.
70839
The report output when processing Express Payments, was displaying an out of balance error when a Termination payment with a Net value of 1,000,000 or higher was included. The report values will now be calculated and displayed correctly.
69979
The Payroll Register report will now display all A/D Code and Hours Type Code total values separately as expected; even when the payrun includes an A/D code and an Hours code which have matching codes and descriptions.
75636
Preceda will no longer allow generating duplicate Payrun Header records for the same Pay environment, to prevent an error when two sessions of Payrun Process are simultaneously run.
75707
Retro calculation has now been updated to show correct results when changes are made to non-effective dated information between the time of creating the Payrun Header and running the Payrun calculation processes.
54181
Transactions will now be cleared correctly after payrun has been reset and Self Service Clear process will run successfully.
Version 15.8.07
Enhancements
Administration
68441, 68437
This enhancement enables Preceda users to calculate certain leave payments using an employee's Average Hours. This feature eliminates the manual involvement in leave payment calculations based on average hours, while maintaining the Australian LSL legislation compliance across all Australia States & Territories as well as several Industry or employment specific Acts & agreements covering LSL.
This solution has been implemented in accordance with the legislative requirements on how LSL should be paid. Average Hours are generally used for casual employees, those who do not have fixed base hours or work patterns, but they can also be required for permanent employees.
Below lists the new capabilities and updates implemented for this enhancement:
New Capabilities
-
Average Hours Payment Rule
-
This new setup screen facilitates configuring average hours payment rules linked to the required legislative average hours. The navigation path for this new screen is Payroll > Reference > Leave Rules > Average Hours Payment Rule.
-
The Average Hours Payment Rules provide directions to determine applicable employee Average Worked Hours to be included in the assessments for processing leave payments.
-
Upon setting up the payment rules, they can be attached to Leave Accrual Methods and/or employees Leave Entitlement records.
-
-
Enabled Leave Units for Australias
-
Leave Units has been introduced to Australia as an optional feature.
-
This feature is enabled when Preceda Variable *PP_LEAVE_UNITS_AU is set to Y.
-
The Leave Units field can then be enabled on Entry via Single Screen (EvSS), Retro EvSS, Express EvSS, Termination EvSS, Prepay/Rebank EvSS.
-
The Leave Units field can be used to control the number of Weeks/Days related to a leave transaction, to override Preceda's default logic for calculating the Weeks/Days from the Hours Amount provided. For example, it can be used to control the Weeks for Average Hours Payments and the Days for Domestics Violence Leave payments, etc.
-
-
Legislative Average Hours Information Screen
-
This is a new read-only screen which displays information related to corresponding leave entitlements. This includes the details of the average hours payment rule, average work hours, and legislative average hours information for a selected employee record.
-
Average Hours Information Screen can be accessed via following screens:
-
Entry via Single Screen - Pay Enquiry screen
-
Express Payments - Calculated Payment screen
-
Termination Wizard - Calculated Payment screen
-
-
-
New Payrun Reports for Leave Payments using average hours (Summary/Detail)
-
There are two new Spoolfile Reports (Summary and Detail) introduced for Leave Payments by Average Hours that can be used by Payroll officers to assist with validating and external reporting of average hours related payments.
-
Existing Screen Enhancements
-
Leave Entitlements and Leave Accrual Method
-
The Average Hours Payment Rule configuration option field has been added to both the Leave Entitlements Drilldown and Leave Accrual Methods screens.
-
For the Leave Entitlements - this field can also be added as a read-only column to the main leave entitlement browse list. Please note that it is only necessary to add an Average Hours Payment Rule to the employee's Leave Entitlement record if wishing to override the Rule configured against the Leave Accrual Method.
-
-
Pay Enquiry
-
Pay Enquiry screen has been enhanced to support average hours payments. Following additional information has been added to the Pay Enquiry screen:
-
Three (3) new optional columns have been added to browse list:
-
Hours Paid by Average Hours
-
Average Worked Hours
-
Average Payment Rules
-
-
-
New notificationson the top message panel
-
New button link to open the Average Hours Information screen.
-
-
Leave History
-
Average Hours information has been introduced to the Leave History browse list and drilldown page. These new fields will now be displayed:
-
Average Hours - this field displays Average Work Hours of the respective employee as at the leave payment date.
-
Hours Paid by Average Hours - this field displays the total hours paid in this transaction which is calculated based on the Average Work Hours.
-
Average Hours Payment Rule - this field displays the corresponding Average Hours Payment Rule which was used for the payment processing to determine applicable average hours work.
-
-
-
Earnings History - Timecard Cost History
-
This screen is accessed by drilling down multiple times on an employee's Earnings History record. The view has been updated to display Average Hours Information, if applicable. The following fields are now available:
-
Average Worked Hours
-
Hours Paid by Average Hours
-
Average Hours Type/Description
-
Average Hours Payment Rule/Description
-
-
-
Express Pay Wizard
-
Express payment wizard has been enhanced to support leave payments using average hours. This update is applicable for both Australia and New Zealand versions.
-
Express Pay Wizard - Calculated Payment drilldown pages have been enhanced to display additional information to support average hours payments.
-
Leave Units can also be used as an optional feature in Data Entry browse list for express payments when Preceda Variable *PP_LEAVE_UNITS_AU = Y for Australian version.
-
Preceda can now automatically apply the applicable average hours payment rule to determine the required average work hours for leave payment calculation.
-
-
Termination Wizards
-
Termination wizard has been enhanced to support leave payments using average hours. This update is applied only to Preceda Australian version.
-
Average Hours Payments only applicable if the terminating employee is configured to pay by average hours and corresponding average hours payment rule is enabled to use in terminations.
-
Termination Wizard - Review Long Service Leave page and Calculated Payments drilldown pages has been enhanced to display additional information to support average hours payments.
-
Leave Units can also be used as an optional feature in Data Entry browse list for termination payments when Preceda Variable *PP_LEAVE_UNITS_AU = Y for Australian version.
-
Preceda can now automatically apply the applicable average hours payment rule to determine the required average work hours for leave pay outs on terminations.
-
The Termination Report has been enhanced to display average hours information if applicable.
-
-
New System Health Checks
-
New System Health Check messages have been introduced to highlight employees who are configured to pay by Average Hours (i.e., configured with a payment rule), but no applicable Legislative Hours exists in their Average Hours Summary.
-
This new health check record is listed under the System Health Check Employee Information section.
-
When the eye icon is clicked in the health check record, you will be redirected to the applicable employee records in Average Hours Summary screen.
-
-
New Payrun Messages
-
New Payrun Messages have been introduced for leave payments using average hours in the current Payrun.
-
-
New Payrun Reports for Average Hours Payments
-
Two new Payrun spoolfile reports (summary and detail) have been introduced for average hours payments transactions. These files can be used for validating average hours payments transactions processed in current Payrun.
-
These two files will be generated at the Update Payrun process and should be available for review at Master File Update Complete status.
-
In addition, new Sort/Selection criteria has been introduced for the above two reports.
Note that you could also add these two new reports to Payrun Dashboard download list via the Payrun Register screen.
-
Process Updates
-
Payroll Processing
-
The Payroll process has been enhanced to support average hours payments. System automatically applies the average hours payment rules where required, to determine the applicable average work hours for leave payment calculation.
-
For Preceda NZ version, if Pay by Units flag is enabled in a corresponding Hours Type Code record, system will ignore Average Hours Payment Rules and will use the Pay by Units calculation logic.
-
-
Retro
-
Retro calculation process has been enhanced to support average hours payments.
-
Following conditions apply for Retro transactions on Average Hours Payment:
-
If the Retro transaction is on existing average hours payment, the original Average Worked Hours from Time Card Cost History will be used for retro adjustments.
-
If the Retro transaction is a new EvSS entry, (i.e., missing payment) the present Average Worked Hours as at transaction date will be used.
-
-
-
Leave Liability Movement
-
Leave Liability calculation process has been enhanced to support average hours payments.
-
System will use applicable Average Hours if a corresponding Leave Entitlement record is configured with an Average Hours Payment Rule which has the Use in Termination / Leave Liability Movement flag selected.
-
-
Company Transfer Process
-
Company Transfer process has been enhanced to support average hours payments. Pay by Average Hours will only be applied when paying out available entitlements which have an Average Hours Payment Rule with Use in Termination / Leave Liability Movement flag selected.
-
Reports Updates
-
Pay Slips
-
Pay Slips have been enhanced to support average hours payments.
-
Additional information in relation to Average Hours payments will now be printed in the employee's pay slip, if applicable.
-
Hours Paid by Average Hours will be displayed under the Hours/Unit if the respective leave payment performed using average hours.
-
-
Leave Liability Report
-
This report will now calculate leave liability based on average worked hours when relevant. Note that this is applicable only if the corresponding Average Hours Payment Rule is enabled for Leave Liability Movement.
-
This report now prints Average Hours as at report date for respective employees.
-
-
Termination Wizard Report
-
The Termination Wizard Report has been updated to support Average Hours Payments. Only the AU termination report is updated in this release. Note that Average Hours information will only be included if the corresponding Average Hours Payment Rule configured to pay in Terminations.
-
-
Timecard Entry (TCHAD) Report - AU version
-
Due to the introduction of Leave Units and average hours payment feature, Time Card Entry report has been enhanced to display leave splits and addition information for average hours payments.
-
-
Other Reports
-
All other applicable reports have been enhanced to display additional information for average hours payments transactions.
-
With this change, reports display input / entry hours as the value in the Pay Hours column for all applicable transactions whereas Pay Value calculation is printed based on the applicable Average Worked Hours. To differentiate average hours transactions from others, an asterisk symbol (*) is displayed next to the Payment value of average hours transactions. A legend text has been introduced in the bottom of the report to define the usage of the (*) symbol in these reports.
Applicable Reports:
-
Pay Journal
-
Reconciliation Report
-
Department Paid Hours
-
Costing Report
-
PTD/YTD Hours
-
Service Hours
-
Payroll Register
-
Exception Report Hours
-
-
73703
This enhancement delivers the final phase of Calculate Average Hours Independently from Leave Classifications & Leave Accruals or Legislative Average Hours, introduced in the last release. This solution provides the ability to setup average hours independently from leave accrual methods and leave types. This helps to set up legislative averages against the employee records matching their country/state legislations they can be used in calculations for Leave Payments. This creates the foundation for Leave Payments using Average Hours which fulfills Australia LSL legislation compliancy.
The following updates have been implemented:
New Capabilities
-
Average Hours Summary History screen
-
A new Average Hours History button has been added to the Average Hours Summary screen, where when clicked opens a new Average Hours Summary History screen.
-
This screen displays the change history records created by manual changes and system updates. System applies a smart filter to display all manual changes as the default option. Standard filter options and pagination options are also available on this screen.
This feature provides quick visibility to Average Hours Summary History.
-
-
Average Hours Summary - Detail Report
-
This new report can be accessed via Administration > Reports > Leave > Average Hours Summary Detail Report option.
-
Upon execution of the report, Preceda will generate separate csv files to the Console > Data Files for all applicable employees. System will also generate an extract (PRP571R1 report) for Average Hours Summary Detail Report.
-
This report will display applicable employee's detail records and earning history records.
This report provides the ability to validate and reconcile Average Worked Hours vs Average Hours Detail and Earnings History records. Furthermore, this helps to eliminate extensive manual work in preparation of Average Hours information.
-
Existing Screen Enhancements
-
Average Hours Enquiry screen
-
Two (2) new read-only fields have been added to this screen:
-
Status
-
Paid Up to Date
-
-
-
Average Hours Detail Screen
-
Pagination has been introduced to this screen.
-
The Average Hours Details records generation process has been improved
-
-
Average Hours Summary Screen
-
The Average Hours Rule prompt has been set to read-only for existing records in the browse-list. You will need to use the drilldown screen to change the Average Hours Rule attached to existing records.
-
65794
Preceda (NZ version) uses Leave Units to record the number of days or weeks taken for leave, which are used for checking and updating employee leave balances. When an employee submits an Annual Holiday leave request via Self Service option (My Leave) and this leave is imported to payroll, Preceda automatically calculates leave units in weeks by referencing the number of days in the leave request. Previously, Preceda used the ratio of leave days taken vs. days in week to calculate applicable leave units for leave applications. However, this calculation logic is not suitable for some customers who have employees with work patterns that consist of days with varied hours.
To preserve the existing functionality while meeting specific customer business needs, a new configurable option has been introduced to use either Days or Hours ratios for calculating the applicable leave units (in Weeks) for employee leave submissions while executing the Import Self Service Transaction to Payroll process.
For this enhancement, a new radio button field labelled Convert to Leave Units on Hours or Days has been added to the Self Service Options screen. Depending on the selected configuration option, the following rules will apply for calculation of leave units in weeks:
-
When option is set to Hours, leave units will be calculated based on prorated Hours in respective work pattern (i.e., ratio of leave hours vs. total weekly hours of the work pattern).
-
When option is set to Days, leave units will be calculated based on prorated Days ratio in respective work pattern (i.e., ratio of leave days vs. total days in the applicable week). This option is applicable for employees with work patterns.
Days is set as the default selected option.
Integration
74892
The Preceda to Dayforce Migration uses a series of Dayforce Data Load Extractor views designed specifically for use with the Dayforce Activate tool, to quickly and seamlessly setup and configure a customer's Dayforce instance, and onboard their employees.
For this enhancement, the process and efficiency of migrating Preceda customers to Dayforce via Activate has been improved.
Below lists the improvements implemented:
-
For Preceda customers that are not requiring Integration between products, a new option, M, has been added to Position 1 of Preceda Variable *PP_DFI_STATUS. For these customers there is no need for generating export files during Close Payrun or displaying the File Submission screen. They only require access to the features related to migrating data from Preceda to Dayforce.
Preceda Variable Position 1 Options Description *PP_DFI_STATUS M Dayforce Migration features are enabled.
-
Dayforce Configuration screen & Extractor view is available.
-
Dayforce Data Loads Extractor views are available.
-
-
The existing Dayforce Data Load Extractor views have been refined to improve alignment with current Activate templates.
-
Extractor View for Dayforce Employee Data
-
The Employee Data Extractor view has been updated to exclude all 'R' version employees.
-
A new field, Middle Name, has been added to the Employee Data view.
-
-
Extractor View for Dayforce Employee Address Data
-
The Employee Address Data Extractor view has been updated to exclude all 'R' version employees
-
The Employee Identifier field has now been updated with the correct spelling.
-
-
Extractor View for Dayforce Site Addresses/Org Site Data.
-
The Location field is a linked sub-report displaying that the extractor view only includes Location Details which are attached to the employees from Payrun Groups selected as an Integration Candidate on the Dayforce Configuration screen.
-
-
Extractor View for Dayforce Legal Entity Data
-
The Level 1 field is a linked sub-report displaying that the extractor view only includes legal entity details for Employer Information records which are attached to the employees from Payrun Groups selected as an Integration Candidate on the Dayforce Configuration screen.
-
The logic on how to populate the Company ID field has been updated:
-
When database is AU, the Company ID field will be the same value as the ABN/WPN from Employer Information screen.
-
When database is NZ, the Company ID field will be the same value as the IRD Number from Employer Information screen.
-
-
-
Extractor View for Dayforce Personal Data
-
The Common Name field in the Personal Data view will be populated with the same value as in the Preferred Name field from the Personal screen.
-
-
Extractor View for Dayforce Work Pattern Data
-
Below is the summary of changes implemented for the Work Pattern Data Extractor view:
Position 1 Options Description XRefCode This has been removed. EmployeeNumber Employee Identifier FirstName First Name LastName Last Name ContractXrefCode Work Contract StartDate Effective Start Date Effective End Date BaseHours This has been removed. WorkPatternLengthDays Work Pattern Length Days WorkPatternDayIndex Work Pattern Day Index ShiftTypeXrefCode Shift Type ShiftTimeBegin Shift Time Start ShiftTimeEnd Shift Time End NetHours Net Hours OrgXref Organization XRefCode This has been removed.
-
-
Extractor View for Dayforce Tax Information NZ
-
The Tax Information NZ Extractor view has been updated to only include employees from the Payrun Group/s selected as an Integration Candidate on the Dayforce Configuration screen.
-
-
Extractor View for Dayforce Tax Information AUS
-
The Employee Identifier field has now been updated with the correct spelling.
-
-
Extractor View for Dayforce Employee Superannuation Data
-
This view has been updated as it previously does not fully cater for all types of Allow/Deduct codes relating to employer and employee Superannuation contributions.
-
The Contribution Type field has been updated to check the Classification of the A/D Code when A/D Type = SUPR to ensure that this field is populated with EMPLOYER or VOLUNTRY correctly.
-
The Contribution Amount field has been updated to populate the related amount when the A/D Classification = 3 or 4.
-
The Contribution Percent field has been updated to populate the related percentage when the A/D Classification = 8, P, or R.
-
The Apply Quarterly Max Base Cap for ER SA field is now set to YES if the Check Maximum Earnings field on the Superannuation screen is checked.
-
-
-
Extractor View for Dayforce Emergency Contact Data
-
The following corrections and updates have been implemented for the Emergency Contact Data Extractor view:
-
Last name is spelt correctly, but Activate is case sensitive and requires this field to be Last Name.
-
This has been updated to exclude all R version employees.
-
Employees with no contact details in Preceda will now be excluded from this file.
-
The Country field is a mandatory field, so it will be populated based on the Operating Country of the database:
-
For New Zealand, the value will be NZL.
-
For Australia, the value will be AUS.
-
-
-
-
Extractor View for Dayforce Contact Info
-
The following corrections and updates have been implemented for the Contact Info view:
-
Extractor View for Dayforce Tax Information AUS
-
Last name is spelt correctly, but Activate is case sensitive and requires this field to be Last Name.
-
This has been updated to exclude all R version employees.
-
The Country has been updated so it will be populated based on the Operating Country of the database:
-
For New Zealand, the value will be NZL.
-
For Australia, the value will be AUS.
-
Note that these are also added as Report Manager Packages.
-
Access to the Report Manager Package will only be possible if Position 1 of Preceda Variable *PP_DFI_STATUS = A or M
-
-
-
-
New Extractor Reports and Report Manager Packages have been introduced
-
A new Extractor Report - Getting Started has been created. This is a one click process to run all of the Activate Getting Started Data Loads via Report Manager.
This report is available in both AU and NZ environments.
-
The main report will contain all fields from Employee Data Extractor View, with sub-reports for the fields from:
-
Employee Address Data Extractor View
-
Site Addresses/Org Site Data Extractor View
-
Legal Entity Data Extractor View
-
-
Access to this Report Manager Package will only be possible if Position 1 of Preceda Variable *PP_DFI_STATUS = A or M.
-
-
Below lists the other newly added reports.
Australia
-
Personal Data
-
Contact Info Data
-
Emergency Contact Data
-
Manager Direct Data
-
Employee Balanced Data
-
Work Pattern Data
-
Fresh Start Employee Data
-
Direct Deposit Data AUS
-
Tax Information Data AUS
-
Employee Superannuation
New Zealand
-
Personal Data
-
Contact Info Data
-
Emergency Contact Data
-
Manager Direct Data
-
Employee Balanced Data
-
Work Pattern Data
-
Fresh Start Employee Data
-
Direct Deposit Data NZ
-
Tax Information Data NZL
-
-
-
The Dayforce Readiness section of System Health Check has been updated to assist with preparation and cleansing of customer data.
-
A new Download button has been added, beside the Eye icon, to the items with exceptions.
The downloaded file will be in Mapper CSV format - where available - with a record for each exception from the check, populated with the employee ID or reference table code relating to the exception.
Below is a list of the Dayforce Integration Readiness System Health Check items that will have the exception file Download button available:
Health Check Item CSV Format Dayforce - Employee Date of Birth must nost be blank M000211/M000211NZ - Personal Dayforce - Employee Country must not be blank Dayforce - Employee State/Region must not be blank Dayforce - Employee Position Location must not be blank M000211/M000211NZ - Personal Dayforce - Position Location State/Region must not be blank M000083 - Location Details Effective Start Date Dayforce - Position Location City/Suburb must not be blank Dayforce - Employee bank split Account Number must not have dashes or alpha characters M000656/M000656NZ - Bank Details Dayforce - Employee Costing Department must not be blank M000213 - Costing Details Dayforce - Employee must not be linked to a Salary Code M000214 - Change Pay Rate Dayforce - Employee Base Pay Rate Frequency must be either A or H Dayforce - Employer Country must not be blank No Mapper - Generic CSV format Value will be "SYVLMSCX" Dayforce - Employer State must not be blank
-
Payroll
74798, 75578
The PAYG Tax Report process has been updated to make use of the EFT Security feature, which provides the option for outputting the PAYG bank file to a secure Collection folder; instead of the Payroll team member downloading the file from the Console.
When the Download PAYG Tax File process is run, the program now references Preceda Variable *PP_EFT_SECURITY to determine where the Bank File is to be output to:
-
If Position 32 = 'Y' - Bank File will be saved to the Collection Folder.
-
If Position 32 <> 'Y' - Bank File will be output to the Datafiles tab of the Console for the User who ran the process.
Additionally, the following updates were also implemented:
-
A new option has been added to Preceda Variable *PP_EFT_SECURITY to control the Collection Folder File Name format.
-
If the Position 33 = P, the Pay Group name will be used as prefix for the file format (PayGroupCode_PAYGTAX_EFT.aba)
-
If the Position 33 is Blank or not P, the default file format will be used (PAYGTAX_EFT.aba)
-
-
A new option has been introduced to Program Control PR423 to enable Payrun Group as a mandatory selection.
-
If PR423 Position 20 = Y, the Payrun Group is set as a mandatory field to run the PAYG report.
-
If PR423 Position 20 = not Y, the Payrun Group is not set as a mandatory field to run the PAYG report.
-
74791
The following updates have been implemented to improve the generation of Flexibility Notes in Pay slip:
-
The Pay slip will now only display a single note for each distinct Hours Code used for leave payments to make the Flexibility Notes more readable and understandable for users, especially if a significant number of Flexibility Leave records exists in a single Pay slip under the same Hours code.
-
When generating multiple Pay slips, Flexibility Notes will only be displayed in the applicable Pay slip.
48690, 72410, 74363
The Payrun Dashboard has been updated with several enhancements for this release.
Below lists the updates for the Payrun Dashboard:
-
Configurable Gross Variance
-
View and Download Reports
-
Reset Payrun Reason
Configurable Gross Variance
The Payrun Dashboard displays two (2) statistics reporting Gross Variances between the current and previous payrun results, with the criteria of the statistics being pre-defined by the system. Based on customer feedback and suggestions, the variance values have been updated to be configurable at a Payrun Environment level, so you will be alerted with the Gross Variances that are relevant for your each payrun group. Through being able to configure the gross variance values, it is possible to achieve a more precise and purposeful comparison, thereby improving statistical analysis efficiency.
The Gross Variance displayed in the Payrun Dashboard can be configured via Payrun Register and Payrun Header screens.
-
Two (2) new fields have been added to both screens: Paid with Gross Variance Over 1 and Paid with Gross Variance Over 2.
-
By default, the Paid Gross Variance Over 1 field is pre-filled value of 500 while the Paid Gross Variance Over 2 is 10000.
-
The Gross Variance fields in the Payrun Header screen will simply retrieve the amount available in the Payrun Register screen. If blank, it will also automatically set up Paid Gross Variance Over 1= 500 and Paid Gross Variance Over 2 = 10000.
-
Payrun Header screen's Gross Variance Value can be overridden and will not impact the original source and the value that will be used for next time.
-
Note that the allowed values for the fields are positive non-zero number and the second value must be greater than the first value.
-
When the new values are saved, the statistics on the Payrun Dashboard should reflect the new results when the Employee Payrun Statistics are next updated.
View and Download Reports
Users can now view and download reports easily from Payrun Dashboard screen instead of having to use the Console.
To enable this, users need to tick the new checkbox fields available in the Report list section of the Payrun Register screen:
-
Dashboard Review - when ticked for a particular report, it will allow Users to review the report from Payrun Dashboard screen.
-
Dashboard Download - when ticked for a particular report, it will allow Users to download the report from Payrun Dashboard screen.
Note that the Payrun ID where the reports were enabled to be reviewed and downloaded needs to be saved as an active environment via Change Payrun Environment screen for the reports to be available in the Payrun Dashboard screen. When it is not selected as an active environment, the Reports module will display in the Payrun Dashboard screen but will be blank.
The Report module will be available on the Payrun Dashboard screen, listing all the reports that have been configured accordingly.
Reset Payrun Reason
When resetting the Payrun via the Dashboard, a pop-up window will appear allowing the users to input a reason summarising why the Reset was performed. This record will be useful for the users to track payrun actions and error management. Note that this is an optional step, users can still process payrun reset without any reasons recorded.
-
The pop-up window has two fields: Reset Payrun Reason and No. of Corrections.
-
Reset Payrun Reason field supports up to a maximum of 100 characters.
-
No. of Corrections field accepts blank, 0, or any positive number less than 9999.
-
-
To report over the information entered in the new Reset Payrun Reason field, a new extractor, Payrun Reset History has been introduced.
It can be accessed via Extractor>Payroll>Reports>Payrun Extract>Payrun Reset History. The available fields for the extractor view are the following:
-
User ID
-
Payrun ID
-
Payrun Environment
-
Pay Group
-
Pay Period End Date
-
Job Start Date
-
Job Start Time
-
Reset Reason
-
No. of Corrections
-
74363
Performance improvement has been applied for customers using the inside Payrun Hours based Leave Accruals process.
A significant Payrun performance improvement can be expected when using this feature and there are many terminated employees in the current Payrun Group.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
75057
The Base Rate Equivalent as at date field in the Salary screen will now display the correct effective start date value for an employee with a Salary Code attached. This improves the information displayed in the scenario where the Salary Code has had a rate change, since the date the Salary Code was effectively dated on the employee.
73696
The Certification Gap extractor now displays and generates records for past positions correctly.
74428
The Company Transfer process now correctly carries forward the Contract Paid Amount of the employee to the new active version of the employee.
68553
An error message will no longer display when Mapper M000222E is submitted to change an employee to a Position that contains Payroll Defaults; where the defaults have no Salary Code/Pay Rate information.
Successfully accepted Mapper records will now update changes on the correct effective date and rejected Mapper records will not perform any updates. An error message on Mapper Summary Report will only appear when applicable.
73148
As the character length limit for Salary Codes has since been increased from 4 to 10, this has now been corrected so that a maximum of 10 characters can be entered into this field via Extractor.
74412
As the character length limit for Salary Codes has since been increased from 4 to 10, this has now been corrected so that a maximum of 10 characters can be entered into this field via Extractor.
72618
Employees being hired with a Future hire date into a Position using Payroll Defaults will now correctly apply the Average Hours Rules; if configured in the defaults.
70984
When a past effective dated transaction is saved, the Effective Date field in the Maintenance History Drilldown screen will now show the correct actual effective date of the record.
74825
When a past effective dated transaction is saved, the Effective Date field in the Maintenance History Drilldown screen will now show the correct actual effective date of the record.
73512
Post Code field should be always editable regardless of the value of the State/Code. Thus, if a record is assigned a value of 11, the Post Code will no longer be updated to 9999 and be locked. Users will now be able to edit it as expected.
53684
Changes in Salary Code are now correctly reflected in the employee's current salary record and corresponding files. The Employee Masterfile is now updated when the Salary Code used by the employee is updated and the update affects their current salary record.
72325
When deleting the historical Salary Code for an employee from the Service Hours window, the Service Hours Details records will now also be removed accordingly. The delete function has a consistent behavior between the current and non-current records. This eliminates problems with reusing the same Salary Code, and expecting the service hours count to start over.
74848
Changes made via Mapper to an employee's STP Employment Basis now correctly updates their Tax Treatment Code information accordingly.
Framework
72128
The password that is automatically generated when the Reset Password process is triggered has been corrected to no longer use the ‘ character when found in the employee's name. The automated password will now just use a random 10 character instead so no error will occur when user uses it in the Reset User screen.
67303
When the Primary Manager approves a leave request, the Secondary Manager (with delegation enabled) will no longer receive an email advising them of the primary manager's approval. The delegation process is now correct so when the Primary Manager approves application, only the employee receives the email verifying approval.
Organisational Management
68852
Mapper M000084 showed an error message after successfully updating some Organisation Units, advising that the record could not be found. Changes have been made to the creation and updating of Organisation Units, which will reduce or eliminate the scenario leading to the incorrect error message being displayed.
Payroll
74366
When an employee on a Work Pattern with 0 hours has an effective dated change in the pay period, the standard recurring Allow/Deduct codes will no longer be dropped. The Pay Period will display the Standard A/Ds accordingly.
64724
If an A/D was entered in express pay Detail Entry screen, and the A/D had previously existed with a value that is the same as the data entry value, the A/D was not being paid via the express payment. This has been corrected to ensure that all Allow/Deduct records are paid accordingly via Express Pay/Termination Wizard.
74232
The Allow/Deduct Rules will now be applied accordingly if the A/D for the employee has an effective dated split during the pay period due to maintenance changes. There will no longer be partial deductions processed when set not to on the Allow/Deduct Code as the system has been corrected to use the original value of the A/D before splitting instead of treating each generated entry individually. Employees will now receive the correct payment.
74917
The AU Year End Reconciliation process now correctly handles negative Year to Date (YTD) values when Allowances/Deductions are set to be reported separately. The Taxable Allowance is now subtracted from Gross whether it is a negative or positive value; thus, the YTD Status window will no longer show an out of balance in this scenario.
75576
Saving of changes to the Payrun Header have been improved to prevent updates while the payroll is in progress. This will no longer be allowed, as expected.
59459
An email pay slip will now be correctly generated when there is a costing adjustment for an employee. The employee with the costing adjustment will receive their pay slip through email as expected.
60409
Under some rare circumstances, overrides entered against an employee's pay slip or data entry transactions was not being cleared successfully during the Close Payrun process. This has been corrected to ensure that details from processed pay slips will no longer be retained in Entry via Single Screen (EvSS), Overrides and Prepay/Rebank Entry screens.
54648
The error message "Hours entered...more than Scheduled Hours..." on Entry via Single Screen was being displayed incorrectly for some employees with historical versions on different Base Hours to the current version. This has been corrected to ensure that the message is only presented when the hours entered exceed the employee's current Base Hours value.
61496
When using the View Selected Pay slip button, the Pay slip information of an employee with existing multiple historical payments containing the same dates and values will now correctly display.
60312
The calculation for the Employer Superannuation Contributions Tax (ESCT) has been updated to ensure that the result is correct for the total Employer Contribution over the full pay period, in the scenarios where the Employer Contribution A/D Code does not have "ESCT Gross-up” set to "Y".
The ESCT will now display the correct calculated value when there is an Effective Dated change within the pay period.
72577
The Period End Non-Contributory Report is now arranged in a correct sequence according to Program Control A442, and the Standard Amount % now has the correct value and will not display the ID Number of the employee. All other values are now correctly displayed as expected.
74447
The Retro Pay process results were not as expected for an employee who had been through a company transfer which also included a change of pay frequency. This has now been corrected to ensure that the pay frequency of the employee is correctly identified for each historical period included in the Retro.
73989
When the Roster assigned to the employee is changed via the Time Details screen, the information available in the Individual Primary Rosters screen & Extractor reports now updates accordingly. The new Roster information should now be displayed correctly, with details from the previous Roster Code related to the updated effective period removed.
72323
When a User changed Payrun Environments after submitting the Generate Retro Pays process, but before the process had been completed, the process may not have produced any results. This has been corrected to ensure that changing Payrun Environments during or before the Generate Retro Pays process start will no longer disrupt the retro pay generation so the necessary retro pay will be successfully generated.
74775
The Leave Units Taken will now correctly display a negative value when the related Time Code Maintenance record is set with "Negative Value" = 'Y' and "Leave Units Processing" = 'Y' (Value equals 1). Additionally, the Pro-rata calculation will now be more accurate.
73507
The Reconciliation MEC Report will now display the User, Date, and Time information correctly.
66579
Retro will now correctly reverse and recalculate over an Express Payment with leave.
59490
Under some rare circumstances, certain details used in the SGC calculation for an employee were not being cleared before the next employee's calculations were performed. This has been resolved to ensure that all information pertaining to previous employees is cleared, before commencing an employee's SGC calculations.
70901
The termination payment's tax calculation for the new Financial Year (FY) is now correct even when the current FY earning is zero. In this scenario Preceda looks at the previous FY earnings to properly calculate the average weekly earnings required for tax calculations.
74390
The component value displayed on the Pay slip created at the end of the Express Pay Wizard should now always correctly match the component values displayed on the NZ Termination report.
Version 15.8.06
Enhancements
Administration
69681
This enhancement facilitates the ability to include Hours Codes in some Leave Accruals, while excluding the same Hours Codes from other Leave Accruals. This is to cater for scenarios where some hours processed for an employee need to be included in the worked hours based leave accrual calculations for some leave types, while being excluded from the accrual calculations for other leave types.
Following display some examples of leave legislations which can be implemented by this feature:
-
The Victorian LSL legislation specifies any period of unpaid leave or unpaid parental leave up to 52 weeks leave will count towards service and accrue LSL.
-
The Victorian LSL legislation specifies any period of unpaid leave or unpaid parental leave up to 52 weeks leave will count towards service and accrue LSL.
-
NT leave legislations specifies absences taken for workers compensation does not count toward services, thus does not accrue Annual, LSL.
This feature improves Preceda's legislative compliance while providing flexibility to exclude Hours Codes from Leave Accruals. The Hour Codes are excluded from leave accruals via setting up an exclusion rule(s) linked to a corresponding Hours Type Code.
Exclusion rules can be set up by either specifying a Leave Classification or specifying Leave Classification & Leave Accrual Method. You can add as many exclusion rules as needed to an Hours Type Code.
-
If an exclusion rule consists of only a Leave Classification, system will exclude the Hours Type Code from all Leave Accrual Methods of the selected Leave Classification.
-
If an exclusion rule consists of both a Leave Classification and a Leave Accrual Method, system will exclude the Hours Type Code from the accrual on this specific Method.
In the Hours Type Codes screen, a new Exclusions button is added beside the Include Hours Worked in Leave Accrual check box. Note that it will only be enabled when the check box is ticked.
Clicking this button will open the Leave Calculation Exclusion Rules drilldown screen, which contains a browse list where exclusion rules can be set up. The drilldown screen allows you to add and delete exclusion rules related to the Hours Type Code. An exclusion rule can be configured as:
-
Leave Type - to exclude all Accrual Methods belongs to the selected leave classification
-
Leave Type and Accrual Method - to exclude a single Accrual Method
Note that only Leave Accrual Methods configured with Pro-rata Method = W (Actual Hours Worked) are applicable for exclusion rules.
A summary message, next to the Exclusions button, will also be displayed to indicate that exclusion rules exist for the Hours Type Code.
67092
There are many Long Service Leave (LSL) Acts across all Australian States & Territories, as well as several Industry or Employer specific Acts & agreements covering LSL, which all have varied recommendations for how LSL is to be paid. The leave payment using an average number of hours per week is one of the most important components, significantly for casual employees and those who do not have fixed working hours. An employee's average hours calculated over the last 12 months, last 3 years, last 5 years or since commencement of the employment, are the main legislative averages required in the various Australian LSL legislations.
In addition, one of the 22 recommendations from the New Zealand Holidays Act Taskforce currently being reviewed in NZ Parliament, is to introduce a new requirement for Average Hours worked over the last 13 weeks to be used in the calculation of Annual Holiday payments for employees who do not have an employment agreement or set roster.
As per above leave legislations, employers are required to calculate payment for LSL taken using an employee's average hours. This enhancement introduces a new capability of calculating and storing the required Legislative Average Hours against employees in Preceda. This enables configuring and generating average worked hours for applicable employees as stipulated in leave legislations. This creates the foundation for future planned updates to enable leave payments using average hours.
The following list of enhancements and new capabilities have been added.
Enhancements
-
-
First Two Column Headings renamed; as now supporting two different Average Hours requirements
-
Added 9 new Legislative Average Hours types (code 1 to 9)
-
Added Suppress Update capability
-
Added 4 new read only informational fields
-
Added new capability of Average Hours Enquiry; to perform a calculation as at Today
-
Added new capability of reporting over Average Hours Summary Change History
-
Extended Tax Weeks field to support more decimal places
-
-
Average Hours Summary Drilldown Screen
-
Added support for 9 new Legislative Average Hours types
-
Added new read only informational fields
-
Extended Tax Weeks column to support more decimal places
-
-
-
Added support for 9 new Legislative Average Hours types
-
Added new Filter option to make viewing specific averages or date ranges easier
-
Extended Tax Weeks column to support more decimal places
-
-
Average Hours Selection Screen
-
Added support for 9 new Legislative Average Hours types
-
Change Y/N prompt list to Check boxes
-
-
Populate Average Hours Details process
-
Added support for 9 new Legislative Average Hours types
-
-
Calculate Average Hours process
-
Added support for 9 new Legislative Average Hours types
-
New Capabilities
-
New Average Hours Enquiry Drilldown Screen
-
New Average Hours Summary History Extractor
-
Average Hours Detail Mapper
-
Supports Add, Update, Delete operations
-
Furthermore, this feature provides the ability to maintain various legislative average hours independently from Leave Entitlements and Leave Accrual Methods, which eliminates existing limitations of the pre-existing average hour's functionality. Beside that Preceda continues to support the existing functionality for using Average Hours in Leave Accrual calculations prior to v15.8.06.
Following displays a summary of applicable State based LSL legislations for casual employees.
This enhancement is being delivered in two Phases, in which Phase 1 has been made available in v15.8.06 while we complete the Phase 2 updates scheduled a separate release later in 2023.
Phase 1 helps you to map all the relevant State, Territory or Industry legislative average hours to your employees in Preceda. This information can now be updated for employees in preparation for Phase 2 where these averages hours can be compared with each other and used in the calculation of LSL payments.
Following describes some detailed information of Phase 1 enhancements and new capabilities added to Preceda.
Average Hours Summary screen
The following updates were implemented for the Average Hours Summary screen:
-
First two column headings of the browse list have been renamed to Average Hours Type and Average Hours Rule.
-
A new list of Average Hours Types is introduced in Average Hours Summary drilldown screen which includes:
-
The default description of Legislative Average Hours can be changed to your own description via edit screen.
-
New columns are added/updated to the browse list of the Average Hours Summary main screen:
-
Tax Weeks Since Hire - This field has been extended to support three (3) decimal places.
-
Suppress Update - this is an editable field (checkbox) and is visible by default. If ticked, this provides the capability to suppress updating Average Work Hours, Hours Worked Since Hire, Tax Weeks Since Hire fields by the Calculate Average Hours, Close Payrun process etc. If this option is not selected (unticked), System will continue updating Average Hours Summary fields as normal.
Note: This feature recommended to select when onboarding new employees from other systems where new employee may not have adequate average hours detail records to calculate average work hours.
-
Last Updated Source - This field displays the last updated source of the Average Hours Summary record. Additionally, new capability has been introduced to record Average Hours Summary change history before updating the Average Hours Summary record.
Available Source options: MANUAL, CALC AVG HOURS, CLOSE PAYRUN, MANUAL DELETED
-
Calculated Period From - This field displays the average hours Calculated From Date used by the calculation process to calculate Average Work Hours for the corresponding average hours summary record. This field value is only visible when Last Updated Source is CALC AVG Hours.
-
Calculated Period to - This field displays average hours Calculated To Date used by the calculation process to calculate Average Work Hours for the corresponding average hours summary record. This is not displayed by default and can be manually added via Columns.
-
Last Updated User - This field displays the name of the user who last updated the Average Hours Summary record.
-
-
New fields are added to the Average Hours Summary drilldown screen to match the columns available from the main screen.
-
A new capability, Average Hours Enquiry has been introduced to enhance the user experience. This feature helps to make an ad hoc enquiry of an employee Average Worked Hours for a selected average hours summary records. This screen can be accessed via the Average Hours Enquiry button from the Average Hours Summary main screen.
The Average Hours Enquiry screen will display Employee Details, Average Hours Rule calculation information and calculated Average Hours information as at current date.
Print Preview option can be used to print this information.
Note: Current version does not support enquiries for terminated employees, and an employee who does not yet have a Paid up to Date.
Average Hours Detail screen
The following updates were implemented for the Average Hours Detail screen:
-
The Populate Average Hour Detail process has been enhanced to support new legislative average hours in which Average Hours Detail records populated based on existing Earnings History records.
-
New Filter option has been added in the screen. There are two (2) filter options: Average Hours Type, and Period End Date.
-
A new list of Average Hours Types is introduced in Average Hours Detail screen drilldown screen which includes:
-
V - Annual Leave
-
L - Long Service Leave
-
S - Sick Leave
-
B-F - User Defined Type B to Type F
-
Average Hours Selection screen
In the Average Hours Selection screen, the field label Leave Classification has been renamed to Average Hours Type which includes Leave Classifications B-F, L, V, S, and the new Legislative Average Hours 1-9.
In addition, Y/N prompt lists are changed to check boxes.
Mapper and Extractor Updates
-
A new mapper, Average Hours Detail mapper (M000219), has been created to populate average hours detail records.
This helps Add, Update, Delete bulk records to Average Hours Detail records.
-
The Average Hours Summary History new extractor has also been added to Preceda. The Average Hours Summary change history records can be obtained via this extractor. This supports same list of fields as in Average Hours Summary Screen.
Framework
Payroll
57390
The Average Rate Rules configuration has been updated to allow the flexibility to have Retro payments included or excluded in the Average Rate Calculations. Additionally, the Calculate Rates Process has also been updated to reference this new option to identify when these transactions are to be included in the calculated results.
Average Rate Rules screen
The following updates were implemented to the Average Rate Rules screen:
-
A new checkbox Include Retro Payments has been added and when ticked, Retro Payments will be included in the calculation.
-
The calculation will only include Retro payments which have a Costing Date within the Average period.
-
Note that this is ticked by default. In case Retro Payments need to be excluded from the calculation, make sure to untick this checkbox.
-
-
The Hours to Use has now been moved to Rule Level. This is a replacement of the previous setting of Position 14 of Program Control PEP39, which will now be obsoleted. Having this option directly from the screen will provide more flexibility in catering for different Average Rate requirements.
-
This is a prompt list field with below options available:
-
B - Use Base Hours
-
C - Calculate Actual Hours
-
-
-
A new field, Rule Description, has been added, which will enable more intelligent searching for Rules.
-
This is populated with a default value based on the length of the Average Period.
-
Calculate Average Rates – Report Updates
As the setting for Hours to Use are now controlled at the individual Average Rate Rule level, the format of the Calculate Average Rate Reports has been updated to support both options being used for the same employees on different Average Rates.
The following updates have been implemented to the report:
-
The order of the columns has been updated. It will now be Value > Average Period > Average Rate.
Note the Average Period column can refer to Hours, Weeks, or Days.
-
The displayed Total Value is always the overall total value for the Average Period.
-
The Base Hours amount is always shown.
Extractor and Mapper Updates
As new fields are added to the Average Rate Rules screen, its corresponding Extractor and Mapper (M000075) have also been updated accordingly.
73829
There is now an option to show the Hours Code YTD Amount on an employee's Pay Slip. The layout of the generated Pay Slip has been updated accordingly to provide room for the YTD amounts when selected to be displayed via the Hours Type Code screen.
In the Hours Type Code screen, a new tick box Show YTD on Pay Slip has been added. When ticked, all standard Preceda Pay Slips will display the YTD amount against the Hours Type Code; otherwise, it will not be displayed. Note that if the Hours Type Code is included in a Pay slip - Codes to Consolidate record, the display option of the Primary code will used, overriding the display option of all Hours Type codes being consolidated under the Primary code.
The new Show YTD on Pay Slip field has also been added to the corresponding Mapper (M000039) and to the following Extractor views:
-
Pay slip History
-
Pay slip Details
-
Hours Type Codes
This new feature is an extension of the Idea: Option to show YTD Super on Pay Slips that has been posted on Preceda Community and has successfully made it into Preceda V15.8.06. To access the links, make sure you are logged in to Preceda Community. |
Time
74350s.
A new option has been introduced for customers who import Self Service Leave Applications to Preceda Time, which will enable the distribution of hours from a leave application to be determined from the employee's Roster information in Time. The employee's Work Pattern (or Base Hours) would only be referenced where there is no Roster information for a date.
A new checkbox field, Use Roster for ESS Import has been added to the Payroll Templates > Design Templates screen. Note that this is only enabled when the Import Leave To field is set to T (Time).
-
When ticked, the distribution of hours for each date in the leave application will be based on the following hierarchy:
-
Individual Primary Rost
-
Standard Roster
-
Work Pattern
-
Base Hours
-
-
When unticked, the distribution of hours for each date in the leave application will be based on the following hierarchy:
-
Work Pattern
-
Base Hours
-
Regardless of the option selected, if there are excess hours from the leave application to be distributed, the remaining hours are to be output to the last day of the leave application.
System Management
59930
New System Health Checks have been introduced for New Zealand to better assist users with identifying incorrect configuration of reference tables and/or setup of employee information, which may impact payrun calculations and legislative reporting. The new System Health Checks will specifically:
-
Assist with checking that newly hired employees are setup correctly before their first pay
-
Reduce potential errors in Payday Filing reporting
-
Assist with customers using Dayforce for integration of new hires with Preceda
Health Check | Description | |
---|---|---|
New NZ specific Health Checks for Employees | Employee with no NZ Inland Revenue Department (IRD) Number provided | This new check will identify if any active employees do not have their IRD Number recorded on the Tax Information screen. |
Employee Employer Superannuation Contributions Tax (ESCT) Rate is 0.00 | This new check will identify if any active employees do not have an ESCT Rate recorded on the YTD Gross, Tax & Net screen. | |
Employee check on KiwiSaver Contributions | This new check will identify if any active employees with a KiwiSaver Contribution being deducted from their net pay, are missing the required employer KiwiSaver contributions. | |
Employee's Costing not associated with Employer Information | This check looks at the employee's Costing information to verify that they can be associated with an Employer Information record | |
New NZ specific Health Checks for Employer Information | Employer IRD Number provided | This new check will identify if an Employer / legal entity does not have a Contact Name provided. |
Employer Contact Phone provided | This new check will identify if an Employer / legal entity does not have a Contact Name provided. | |
Employer Contact Phone provided | This new check will identify if an Employer / legal entity does not have a Contact Phone provided. | |
Employer Email Address provided | This new check will identify if an Employer / legal entity does not have an Email Address provided. |
Health Checks for Employees
Health Checks for Employer Information
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
55017
The linking issues in Extractor when adding fields from the Additional Addresses section, such as the State/Region Description field, have now been corrected. The extracted report, with fields added from this section, will no longer be blank and will show the correct information.
71240
The Tax Information screen now accepts Country Codes up to four (4) characters. Additionally, the corresponding field in Mappers for Tax Information (M0000313) and Hire/Hire with Bank Details are also updated accordingly.
70831
The Long Service Leave (LSL) Summary Report now displays the correct value of Entitlement Hours and will deduct the Leave taken to derive the Hours Due as expected.
55895
Entitlements will no longer be moved to pro rata too early when processing leave accruals using worked hours outside of a payrun. The displayed leave entitlements will now be correct.
74368
The Leave Liability Report process now completes successfully, even when an employee has an ESS Claims record. The report displays the correct values, and no error is encountered.
74336
Leave Payouts after Company Transfer are now correctly displaying on the records of the original employee record.
70202
In the Classification screen, the description of Personnel Group field will now display correctly regardless of the record having a value on Share Entered Group field.
Framework
74314
The locking issue for scheduled jobs has now been fixed. The scheduled jobs are now delivered to the recipient on the correct date and time; thus, Report Manager Packages can now access their corresponding tasks correctly. Additionally, affected, and corrupted scheduled jobs have also been restored.
Payroll
69878
Retrospective adjustments which should result in a change to an employee's Complying Fund Superannuation contributions, will now result in this adjustment being processed and included in the results of a Retro Pay calculation as expected.
72324
When the Recipient Details Mapper is imported, the ATO Compliant Verified date field will now be updated correctly.
74604
The duplicate key issues have now been fixed so employee records will no longer be corrupted after running Master File Update for the employees that have been Terminated then Reinstated. Additionally, employee records that were affected and corrupted have been restored.
61732
Employees will no longer be able to bypass the Allow/Deduct Code Filters via Claims screen in ESS. Only claims with an A/D Code made available to the employee will be successfully saved.
56866
The payrun Reconciliation and YTD Integrity Reports will no longer show employees as being out of balance, after Share Scheme payments have been processed for them.
53755
When an employee applies for leave spanning multiple dates across different pay periods, and they reduced the hours away to a value which is lower than the hours for the first period, the Self Service Import is not able to correctly handle the split of the overridden hours to each period. The Leave Calendar feature was introduced to ensure the overridden hours are correctly associated with each date, but a number of customers have not enabled this feature.
To avoid scenarios like this from occurring for customers who have not enabled the Leave Calendar feature, employees will no longer be allowed to make amendments to the Hours Away field when an application spanning multiple dates is being requested. When Leave Calendar is OFF, the Hours Away field on the My Leave request will now be read only when the End Date is greater than the Start Date (ie the employee is taking multiple days of leave). If the employee wants to edit the number of hours defaulted from their Work Pattern/Base Hours, they will need to submit separate applications for each individual day.
Alternatively, the Leave Application Calendar feature can be enabled via the Self Service Options screen, which allows employees to submit applications for multiple dates, with overrides applied to the hours being applied for.
68407
When the Process Email Pay Slips process is run to send postponed pay slips to employees, their Pay Slip will now display the correct details and values, including Retro when expected.
70511
Student Loan calculations, where multiple Pay Separators are used, will now be correct. The Student Loan will be calculated and displayed as expected when Tax Code and Supplementary Tax Code = S.
Time
72074
When using the Advanced Search in Time Module, the search results will now correctly display the employee's status based on the selected Status filter. The filter in Advanced Search now works as expected.
Version 15.8.05
Enhancements
Administration
72424
Preceda has been enhanced to harmonise ESS - Projecting Leave Balances and Projected Leave Accrual Report with flexibility payments. Flexibility payment transactions are now being considered when projecting Leave Balances and generating the Projected Leave Accrual Report.
-
Projecting Leave Balances now refers to the Flexibility Payment Type for pending approved leaves (i.e. approved leave but not paid) so that the number of hours taken from the Flexibility Payment Type will be calculated and deducted from the projected Leave Balance.
Furthermore, the outstanding leave requests (i.e. submitted, approved) are now being referenced when calculating and displaying the projected Leave Balance on My Leave.
-
The Projected Leave Accrual Report now takes Flexibility Payment Type into consideration for pending approved leaves (i.e. Leave Requested, Approved, Imported to Payroll but not paid) when calculating the projected Leave Balance.
The Total Accrued, Total Requested, Imported to Payroll, and Balance after Deduction columns are printing in Hours in the Projected Accrual Report.
-
ESS - Projected Leave Balances are consistent and comparable with the Projected Leave Accrual Report balances.
55929
To make leave liability calculations consistent and comparable across Preceda Leave reports, new configuration options have been introduced to align the date source for leave calculation used for the following reports:
Users are now provided the flexibility to select their preferred date source for calculating leave liabilities. They will have the option to choose either Today's rate or Rate as at Leave Entitlement's Date Accrued To via Program Control LVACC Position 30 or 31, depending on if they are configured with an Effective Dated Pay Rate or with a Non-Effective Pay Rate.
Name | Position | Options/ Value | Description |
---|---|---|---|
Date Source for Calculating Leave Liabilities for Leave Reports for Effective Dated Pay Rates 30 | 30 |
T (or not A) (Default)
|
Use the current date or today's date when calculating employee's leave liabilities for the Leave reports |
A | Use the rate as at Date Accrued To when calculating employee's leave liabilities for the Leave reports | ||
Date Source for Calculating Leave Liabilities for Leave Reports for Non- Effective Dated Pay Rates |
31 |
T (or not A) (Default)
|
Use the current date or today's date when calculating employee's leave liabilities for the Leave reports |
A | Use the rate as at Date Accrued To when calculating employee's leave liabilities for the Leave reports |
Framework
69988
The End Job button has now been removed from the button group of Systems Jobs in Preceda Console. Having this button before has allowed users to end jobs untimely causing hard to fix data integrity issues. In case users feel stuck and really need to end a job, they will now need to contact the Preceda Support team, who will be able to assess the state of the job and end it in a controlled manner where possible.
Integration
72657
As Dayforce only accepts and transfers country details in ISO Code format, the ISO Code field has been added to the Country Codes screen.
This reduces the chance of incorrect or unintentional mapping of the Country Code to another country's Description/Name. Likewise, this identifies existing Country Codes which may be wrongly configured against ISO Standards. Only the correct ISO Country code will be transferred and used in the integration with other systems, such as Dayforce.
72611, 72740
For a smoother cutover plan for Preceda Dayforce integration customers, new extractors are introduced to Preceda's Dayforce Data Loads to match Fresh Start Employee Data and Tax Information NZ templates in Dayforce Activate.
The new extractors will be available if Preceda variable *PP_DFI_STATUS = A. They will be available in the extractor under Dayforce Data Loads.
The Fresh Start Employee Data extractor, will extract the base details of employees, including all the versions and status. This will apply to both AU and NZ customers.
The Tax Information NZ extractor will allow easy reporting over Tax Code related information of employees in New Zealand. This view will only apply for NZ customers.
72795
For easier and smoother data transfer for the Preceda-Dayforce integration, there is now a mechanism to sync the following latest employee information from Dayforce to Preceda:
-
Employee's Middle Name
-
Aboriginal Torres St Isl (for AU only)
-
Gender
-
State per employee's Primary Work Assignment
-
Make Bypass Surname/ Date of Birth Check upon new hire
This will be done through a microservice running in the background every night to retrieve the latest employee information. Such information is formatted into Mappers, uploaded automatically to Preceda SFTP, ready for immediate processing. If Preceda is in a state of allowing Integration to come in, Payroll Managers shall see incoming Mappers via the Inbound Integration screen.
71636
To improve the default mapping and processing of data in a Workday PECI file in the Standard template Workday XML Transformation file, updates were implemented for the following areas:
-
Update default mapping of data for the below Preceda fields
-
Phone Numbers updated to map from <peci:Formatted_Phone_Number>
-
User Date 1 (Adjusted Service Date) mapped from <peci:Continuous_Service_Date>
-
Effective Start Date now mapped for Allow/Deduct updates from <peci:Compensation_Earnings_and_Deductions>
-
-
Improve the handling of Time Off data to better support multiple records for the same date.
The updates are applied to the mapping for Australia and New Zealand, for the two main PECI Event Types that are supported in Preceda's Workday integration:
-
HIR - New employee Hire event
-
DTA - Data change event; for existing employee
Note that this PECI file Transformation / mapping update has only been applied to the Template used for new Workday integration implementations. No changes have been made to existing customer Transformation configurations.
Payroll
73516
In the Allow/Deduct Codes screen, when the values selected for the Classification field is O and for the Year End Print flag (YEPF) field is 0, a new valid option, Task Allowances (AKN), will now be available for STP Payment Type field.
71031
There is now an option to show the YTD Amount of Superannuation, and other allowances or deductions on the employee's Pay Slip. To accommodate this change, the layout of the generated Pay Slip has been updated to provide room for the YTD amounts when selected to be displayed via the Allow/Deduct Codes screen.
In the Allow/Deduct Codes screen, a new tick box Show YTD on Pay Slip has been added. When the field is ticked, the specific A/D Codes YTD amount will display on the Pay Slip, otherwise, it will not be displayed.
Note that if the A/D code has been configured on the Pay slip - Codes to Consolidate screen, the display option of the Primary A/D code will be referenced, overriding the YTD setting of any group item.
The new field has also been added to its corresponding Mapper (M000009) definition, and to the following extractor views:
-
Pay Slip History
-
Pay Slip Details
-
Allow/Deduct Codes
This new feature has been posted as an Idea: Option to show YTD Super on Pay Slips on Preceda Community and has successfully made it into Preceda V15.8.05. To access the links, make sure you are logged in to Preceda Community. |
72656
The Express Pay/Termination processes has been enhanced to record OTP tax messages. Upon completion of the Express Pay/Termination Processing and subsequent Payrun execution, OTP messages are imported to Payrun Messages. This feature provides greater visibility to OTP tax calculations performed in Express Pay and Termination transactions
60299
The New Zealand Inland Revenue Department (IRD) has announced tax changes which will apply from April 1, 2023.
The changes include the following:
ACC Earners Levy / Threshold
-
The maximum income to which the ACC Earner Premium Rate applies increases from $136,544 to $139,384.
-
The Earner Premium Levy is also being updated from 1.46% to 1.53%.
Student Loan Threshold
The student loan repayment threshold increases to $22,828 for the 2023/24 tax years. This is an increase from $21,268 per Year / $409 per week to $22,828 per Year / $439 per week.
The Tax Table Update Button will be available on the Preceda Welcome Page from March 13, 2023. Note that only users who have Administrator and Security Officer set to "Y" in Define Users screen will be able to see the message on the Welcome Page and click on the button.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
49026
When a Company Transfer is performed for an employee, and the date of the transfer is prior to the date of one or more Earnings History records, Preceda creates a Rebank against the old version of the employee (previous company) and a Prepayment against the new version / company. This updates the YTDs for both versions of the employee to reflect the correct income, deductions, and tax for each company. Where the transfer also involves a change of Payrun Group, there was an issue with both the Rebank and Prepayments being created in the new Payrun Environment, resulting in the Rebank not being processed successfully. This has now been corrected to ensure that in this scenario the Prepayments will be created in the new environment and the Rebanks will be created in the old environment; while employees transferred without any change to Payrun Group will have the Prepayments and Rebanks created in the same payrun environment.
55856
Terminated employee records will no longer be included in the report generated by the Calculate Leave Accruals process.
62549
The Leave by Proxy Wizard's employee selection browse list now displays the correct result and employee details where page dropdown or next page arrow is used to navigate between pages.
59680
The report produced by Leave Liability Extract will now include employees with their allotted Annual Leave information when the chosen Leave Classification is Annual.
55973
The Leave Liability Report now correctly applies and calculates liability based on the related equivalent unit types when the option to Print Equivalent Values is selected. The report will now display the accurate equivalent values.
70865
Mapper M999777NZBK / M999777NZ no longer fails when a hyphen is included in the employee's IRD Number. Instead, when the data includes a hyphen or any invalid character, it will be rejected and the error message validation "IRD Number is invalid" is displayed in the mapper report.
Framework
69982
No Runtime Prompt will now occur when running an extract if the Sub Report, which contains the runtime prompt, has already been deleted. The runtime prompt is now correctly removed from the extract.
65163
Prepayments created from an Express Pay or Termination Wizard payment are protected at screen level to prevent them from being modified. It was, however, possible for Prepayments imported via Mapper M000595 to add new Hours or A/D records to these protected transactions. This has now been corrected to ensure that protected Prepayments can no longer be updated via Mapper.
63099
Where a Report Manager package was scheduled to run on the last specific day of the month - for example last Wednesday of the month - the scheduler was adding one month to the run date before looking forward for the next required run date. In the example where the run date was on the 31st of a month and the following month had less than 31 days, this resulted in one month being missed in the schedule. The scheduling tool has now been updated to handle this correctly, to ensure that the reports are run and successfully distributed each month.
69982
Some customers have reported issues with the next scheduled run of a Report Manager package not being set correctly when Daylight Savings starts or ends. Although we cannot simulate the changeover of Daylight Savings, and are therefore unable to fully test this scenario, we believe the that updates applied to the Report Manager scheduler in this release will resolve these reported issues. This should ensure that the scheduled time is maintained on the next run of the package after the Daylight Savings changeover. It is still however a recommendation to avoid scheduling any reports to be run between the hours of midnight and 3am.
Payroll
71345
The Allow/Deduct Report will now display all Allow/Deduct records correctly even if more than 999 Allow/Deduct Codes exist in the database.
66117
When the Recipient Details Mapper is imported, the ATO Compliant Verified date field will now be updated correctly.
59078
When an Hours Code configured for Leave Without Pay (LWOP) was processed for an employee, and this code is to be included in the RDO calculation the resulting update to the employee's RDO accrual was incorrect. This has now been resolved to ensure that it will no longer cause an under accrual for RDO to affected employees.
64158
The Costing Date in the General Ledger (G/L) Open Period file extract of the generated G/L Accrual transactions are now in the correct date format of YYMMDD.
72374
The generated G/L File will now reflect balancing Debit and Credit values even if Leave Movement is active and oncosts exists on leave transactions. The cost is now correctly calculated, and the total amount will be the same regardless of costing split.
56924
During close Payrun, a Leave Classification that do not have an Entitlement record prior to processing the leave will now correctly generate a Leave Entitlement record. The values in the Leave Entitlement also accurately match the values in Leave History.
59929
The employee counts are now debited in the correct payrun environment, even when users change between multiple payruns environments as the Close Payrun processes are running or queued.
73263
The Payrun Dashboard will now load successfully even if more than 9999 messages are available from the Messages group box. Where more than 9999 records exist, the screen will successfully load the first 9999 messages, while this limitation does not apply to the download option on this screen, allowing all messages to be downloaded as expected without causing any error.
60112
The Recipient Name and Reference Number will now be accurately displayed in the generated SuperStream Report according to Pay Period End Date.
64009
The retro calculation for RDO with pay and RDO without pay is now correct. The retro values upon calculation are now accurate even when the RDO hours are split between paid and unpaid in the original pay.
71202
Transactions imported in PAY34T format to Entry via Single screen are now flagged with the correct "Source of Change" information in the Timecard Cost History for databases with Preceda Time activated. This resolves a reported issue with retro calculations to ensure that accurate values are now reflected.
70489
A message wait error will no longer be encountered when consecutive Off cycle payruns are executed in an irregular pay period. Also, this will no longer have a negative effect on the pay processing calculations of Superannuation.
73167
The Study and Training Support Loans (STSL) will now be correct when calculating tax for an employee's OTP, based on the Supplementary Tax code setting of the employee. When Supplementary Tax code is B, the STSL will be calculated on the OTP, while when blank, it will not be calculated.
2368
Employees with zero YTD figures are now successfully excluded from the NZ Year End Reconciliation Report when the criteria option to include Employees with Zero YTD Figures is unticked.
Time
62774
The Hours Worked displayed on the Time History Editor and Time Recording screens are now matched and correct.
72105
The conversion of hours to days (leave units) after importing from Time to Payroll is now correct.
63692
The Pre-Post Times Report is now correct even when using a Start Date prior to the employee's Hire Date. All Time Entries that are only approved by Managers (i.e., no Employee approval yet) are now included in the Pre-Post time Report of Unapproved transactions as long as they are within the date range specified, regardless of whether the date range is before or after the Hire Date.
System Management
72662
The Audit Log will now correctly record and update employee details for changes that are made to the Global ID fields.
Version 15.8.04
Enhancements
Integration
3355, 71270
When integration with Preceda is in place, employees in Preceda might be identified with different IDs in other systems, and those IDs are usually recorded in Global ID fields in Preceda. In this release, the Advanced Search, Payroll Register, and Payrun Messages have been updated to allow searching for employees by Global IDs and Dayforce IDs.
Advanced Search
Global IDs / Dayforce IDs are available in the Advanced Search feature for screens under the Administration, Time, and Payroll folders.
The additional fields can be visible in the search result area when the columns are ticked.
Payroll Register Options / Payroll Register report
More Global IDs / Dayforce IDs are available in the Payroll Register Options screen with initial value of Include in List unticked. When ticked to be included in the list, such fields will become available via Payroll Register Report (csv format) when the report is generated.
Payrun Messages
Global IDs / Dayforce IDs can be made visible via the Payrun Messages screen when the columns are ticked.
When clicked to download the Payrun Messages, the additional columns will be available in the csv file if any value.
This new feature has been posted as a Ideas on Preceda Community and has successfully made it into Preceda V15.8.03. To access the links, make sure you are logged in to Preceda Community. |
71436, 71291
Two new extractors, Work Pattern Data extractor and Employee Superannuation Data extractor, have been added. They will be available under the Dayforce Data Loads folder when Preceda Variable *PP_DFI_STATUS Position 1 = A.
Work Pattern Data extractor
This extractor will allow Preceda Implementation Consultants to easily extract employee's Work Pattern data from Preceda. The output can then be shared with Dayforce WFM Consultants to generate XML files and import into Dayforce.
Employee Superannuation Data extractor
This extractor will allow Preceda Implementation Consultants to easily extract employee's superannuation data from Preceda. The output can then be shared with Dayforce WFM Consultants to upload into Dayforce Activate.
71289
For the Preceda and Dayforce Integration, customers will have the option to hire Dayforce employees in Preceda with their original Dayforce Employee Number.
A Program Control DAYFC is introduced:
Position | Description |
---|---|
Position 14 <> Y (default) |
Must set Auto Generate ID Number = Y via Hire Rules screen. Employees from Dayforce will be hired in Preceda with auto-generated ID Numbers. |
Position 14 = Y |
Must set Auto Generate ID Number = Y via Hire Rules screen. Employees from Dayforce will be hired in Preceda with their Dayforce Employee Number. |
71436, 71291
Two new extractors, Work Pattern Data extractor and Employee Superannuation Data extractor, have been added. They will be available under the Dayforce Data Loads folder when Preceda Variable *PP_DFI_STATUS Position 1 = A.
Work Pattern Data extractor
This extractor will allow Preceda Implementation Consultants to easily extract employee's Work Pattern data from Preceda. The output can then be shared with Dayforce WFM Consultants to generate XML files and import into Dayforce.
Employee Superannuation Data extractor
This extractor will allow Preceda Implementation Consultants to easily extract employee's superannuation data from Preceda. The output can then be shared with Dayforce WFM Consultants to upload into Dayforce Activate.
71289
For the Preceda and Dayforce Integration, customers will have the option to hire Dayforce employees in Preceda with their original Dayforce Employee Number.
A Program Control DAYFC is introduced:
Position | Description |
---|---|
Position 14 <> Y (default) |
Must set Auto Generate ID Number = Y via Hire Rules screen. Employees from Dayforce will be hired in Preceda with auto-generated ID Numbers. |
Position 14 = Y |
Must set Auto Generate ID Number = Y via Hire Rules screen. Employees from Dayforce will be hired in Preceda with their Dayforce Employee Number. |
71253
Introducing the Dayforce Integration Readiness section, which will be available when Preceda Variable *PP_DFI_STATUS position 2 = Y, to the System Health Check screen. Cleaning up the exceptions reported here should align Preceda data with Dayforce validation rules better. It should assist Preceda Implementation Consultants with data preparation before Dayforce Initial Data Load.
Payroll
71161
When generating manifest files for clients who have integration with SuccessFactors, the leading zeroes in the Employees ID may now be configured to be truncated or retained via Preceda Variable *PAYSLIP_COLLECTPosition 2. Where *PAYSLIP_COLLECTPosition 1 = S (SuccessFactors):
-
Setting *PAYSLIP_COLLECT Position 2 to Y removes the leading zeroes in the Employee ID.
-
Leaving *PAYSLIP_COLLECT Position 2 blank, the leading zeroes of the Employee ID will be included in the manifest file.
70818
Further improvements have been completed to provide an enhanced user experience with advanced options in flexibility in taking leave.
Hours Type Code
A new option - Accrue Leave on Actual Hours Paid - has been added to the Hours Type Code screen under Flexibility Payments section enabling you to accrue leave based on the actual hours paid.
An information icon is presented next to Accrue Leave on Actual Hours Paid option, which you can hover over to see some useful information to assist with selection of this option.
This option will be used to enable Preceda for accruing employee leave entitlements based on the actual hours paid for flexibility payment transactions, instead of accruing based on the hours the employee was on leave for. This is only applicable for leave accrual methods configured with pro-rata method Actual Hours Worked.
Enhance User Experience in Other Modules
Flexibility Payment Type has been added as an optional column to Express Pay Wizard and Retro Entry via Single Screen's Hours/Leave browselist as well as on Time Editor's Hours Worked/Leave Hours browselist. This column is hidden by default.
-
Express Pay Wizard and Retro Entry via Single Screen's
When a leave payment record entered with an Hours Type Code linked to a Flexibility Payment Type (i.e., Half Pay, Double Pay), additional information will be displayed related to flexibility payments.
-
Time Editor's Hours Worked/Leave Hours browselist
When a time entry record entered with an Hours Type Code link to a flexibility payment type, additional information will be displayed related to flexibility payments.
The Time Code Maintenance screen has been updated to display corresponding flexibility payment type (i.e., Half Pay, Double Pay) if the selected Hours Type Code is configured with a Flexibility Payment Type.
Leave By Proxy
The Leave Application and Confirm Application Details screens of Leave By Proxy Wizard have been updated to display Flexibility Payment Type details if the selected Hours Type Code is configured with a Flexibility Payment Type. An information icon is presented next to the flexibility payment description in
which the manager can hover over to see some useful information to assist with the leave submission.
Preceda Mobile
Preceda Mobile Application has now been enhanced and made compatible with the Flexibility Payment functionality.
-
When an employee selects an Hours Type Code configured with a Flexibility Payment Type, an acknowledgement message will be displayed in the My Leave message panel to assist with the leave application (i.e., Leave at Double Pay reduces Entitlement by Double the Hours away. Please enter full length of absence into Hours/Days away).
-
Likewise, the Review Leave screen will display an acknowledgement message in the Review Leave message panel to assist with the leave approval (i.e., Leave at Double Pay reduces Entitlement by Double the Hours away. Please ensure Hours/Days away matches full length of absence).
-
Flexibility payment type rules will be applied to calculate leave balances for flexibility leave applications. A Leave Balance warning (i.e., Warning: Applied Leave Exceeds the Available Balance) will be still displayed when the leave balance is insufficient for the leave application based on the relevant Flexibility Payment Type.
Mapper and Extractors
The following Mappers have been updated to support adding or changing of records for Hours Codes using a Flexibility Payment Type:
-
Hours Type Code (M000039) - new fields added
-
Leave History (M000236) - no change to file layout
-
Timecard Cost History (M000234TCH) - no change to file layout
The following Extractors have been updated with additional fields to support Flexibility Payment Types:
-
Hours Type Codes
-
Time Card Entry
-
Retro Entry via Single Screen
71664
When Program ControlPAY42 Position 23 = Y, the handling of multiple bonuses and commissions within the same financial year has been improved to provide a better tax position for employees who receive frequent payments of bonuses and commissions throughout the year. A new option E has been added to Position 24 of Program ControlPAY42 enabling the deduction of the current Year to Date (YTD) OTP Amount from Weekly average earnings.
Name | Position | Option | Default | Description |
---|---|---|---|---|
Deduct Year to Date OTP Amount from Weekly average earnings | 24 | E | Deduct YTD OTP Amount from Weekly average earnings. | |
blank | Do not deduct YTD OTP Amount from Weekly average earnings. |
54389
Restore Library is a complex process and can result in Message Wait issues when customers try to restore from backup of an older version of Preceda. This happens due the difference in file structure between a backup of prior release and the current version. This enhancement improves the robustness of Restore Library by preventing Message Wait issues from happening and redirecting customers to Preceda Support to get assistance in restoration when there are structural differences detected in the backed-up files.
70205
To fully support all Income Stream Types available from the ATO reporting for Single Touch Payroll Phase 2, two new Income Stream Types: IAA and CHP have been added to STP 2 activated environments.
-
Income Stream Type IAA (Inbound Assignees to Australia) is available when the Payment Summary Type is I (Individual Non-Business). At the same time, Home Country becomes a mandatory field.
-
Income Stream Type CHP (Closely Held Payees) is available when the Payment Summary Type is I (Individual Non-Business.
The System Health Check screen has been updated to include the validation of Income Stream Type IAA and Home Country under STP Phase 2 Mapping.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
62654
The annual gross is now calculated accurately and is displayed in the LSL Report Extract correctly even when using different Base Hours or an hourly rate of greater than 100.
59925
The generated Absenteeism Report will now correctly handle employees with multiple versions (e.g., employee that has been transferred or reinstated). The report will display these employees accordingly based on the Report Selection set.
61842, 62206, 64577, 69949
The Calculate Leave Accrual process was producing some incorrect results in some scenarios when there was a change to an employee's Base Hours. The following issues were occurring with certain Leave Accrual Methods:
-
Base Hours change on the first day of new accrual period was not identified, and accrual for whole period was calculated using previous Base Hours value
-
Base Hours change dated within the new accrual period was not identified, and accrual for whole period was calculated using previous Base Hours value
-
Leave Entitlements stored in Days or Weeks were being recalculated incorrectly when there was a Base Hours change in the new accrual period
-
Maximum to Accrue exceeded in some scenarios when a Base Hours change was in the new accrual period
All these issues with the Calculate Leave Accruals process have now been resolved to ensure the results are correct when employees change Base Hours.
57482
The Long Service Leave (LSL) balance no longer gets duplicated to other new leave entitlements when a Position changed is processed, and the new Position includes Defaults to add additional leave classifications to the employee.
54249
Mappers M000222E and M001428 used to change an employee's Position will no longer end Salary Packages when they have successfully updated the employee's Position information. These Mappers are now working as expected.
66102
The correct value of Remaining Balance for leave entitlements will now display accordingly based on the Unit Type (e.g., Days, Hours) selected in Self Service Options, when an employee selects to project the balance to a later date.
62379, 71290
The system will now retain the original information, including the attachments (e.g., Medical Certificate), from the employee leave application submission regardless if leave is paid or converted to unpaid. The Leave History screen will now display the correct leave history information including the attached document.
Framework
68884
The Breakdown of Hours Paid section now correctly displays all the needed information when the Print Preview button is clicked from the Time History Editor screen.
Organisational Management
71922
The Occupants Report was not completing successfully for many customers after the upgrade to 15.8.03. This issue has now been corrected to ensure that the report is generated as expected.
Payroll
71988, 72091
The improvement to Maintenance History information introduced in 15.8.03 resulted in the Calculate Payrun process failing for some customers. This issue has been resolved to ensure that these processes will complete successfully.
66767
When bank split deduction (i.e., A/D Classification K) is processed with a Contract Amount and Partial Deduction ticked, the deduction for the employee is now processed correctly without any overpayment of the contract amount.
71848
Moving the cursor between fields using the Tab key was not functioning correctly in Entry via Single Screen (EvSS) after the upgrade to 15.8.03. This has been resolved to ensure that the Tab key successfully navigates from the Hours Type code field to the next field in the browselist.
72500
When Close Payrun process is run, Payrun Groups that are integrated to Dayforce will have their Earnings Statement generated correctly and successfully.
71828
Extractor files created during the payrun will now populate correctly if employee is terminated via Termination Wizard. The extracted results will also be consistent to what is displayed in Entry via Single Screen (EvSS) and Termination Wizard screen in Preceda.
69883, 67064
You can now successfully run the Time Card Print process without any message wait (i.e. an error that required assistance from the Support Team to resolve) when performing a Salary Code override on Entry via Single Screen using a Salary Code which has a high hourly rate in any of the Pay Rate positions that is not Pay Rate 1.
System Management
72001
The Maintenance History Drilldown original change information will no longer be populated by the system when original change information did not exist. It will also no longer trigger updates on old maintenance history records, so the Change Dates, Time, and user on old records is retained.
70377
The Links screen will now correctly populate and display all available records when searching for any link with lengthy characters as URL or Name.
Version 15.8.03
Enhancements
Administration
62165
The calculation of Leave Accruals based on Worked Hours and the rolling forward of the Date Accrued To on the employee's Leave Entitlement records has only been performed when some Hours Codes configured to be included in the Hours Worked for Leave Accrual are processed in the payrun. In most scenarios where employees receive pay slips that do not include any Hours Codes with this configuration, their Leave Entitlement records remain unchanged with no updates to the entitlements or the Date Accrued To.
Although this may be acceptable to many customers, we were informed that it is not always desirable to leave the Date Accrued To unchanged, particularly when Leave Entitlements are integrated with external T&A or HCM systems which project leave entitlements if the Date Accrued To is in the past.
For customers who are happy with the current behaviour of not moving the Date Accrued To forward unless the employee is paid some Hours that affect the Leave Accrual, there is no need to make any changes. If there is a preference to have the Date Accrued To moved forward when the Leave Accruals are calculated over a period where the employee receives a pay slip, regardless of the paid amount or whether pay slip contains hours that have been configured as 'Include Worked Hours in Leave Accruals', a new Program Control option has been introduced. To update your Preceda database to the new behaviour in this scenario, you can update Position 29 of Program Control LVACC to 'Y'.
Name | Position | Option |
Description |
---|---|---|---|
Leave Accruals on Worked Hours when pay slip has no Hours set to be included in the Accrual | 29 | Y |
Update the Date Accrued To of Leave Entitlements based on Worked Hours whenever the employee receives a pay slip, even when it only includes Allowances or Hours which are not configured to increase the leave accrual. |
N (Default) |
Do not update the Date Accrued To of Leave Entitlements based on Worked Hours unless the employee receives a pay slip containing some Hours configured to be included in the leave accrual calculation. |
69566
Any information changes linked with a future effective date are not immediately reflected in the Employee Maintenance History screen but is updated during midnight by a maintenance program, Active Record Rollover.
During the maintenance program execution, system overrides changed user information by the system user by "PRECEDA" and user change date and time overridden by rollover date and time which distorts original change user information. This has raised confusion among business users.
To avoid such confusion and enhance user experience, the Employee Maintenance History screen has been updated to have new fields to display the Original Changed User information (left information panel) for future effective dated and non-effective dated transactions. These fields will show the original change username, date, and time to which the data was changed prior to the run of the latest Active Record Rollover. The change made by the maintenance program will still be displayed in the screen.
For history transactions, system will populate original user information on the fly when business user opens the maintenance screen drilldown page.
This new feature has been posted as Ideas Preceda Community and has successfully made it into Preceda V15.8.03.
To access the links, make sure you are logged in to Preceda Community. |
Integration
70510
The Global Logon messages have been improved ensuring that the correct error message is displayed based on invalid attempt/s of the user.
-
For any invalid attempts prior to the 2nd last and last attempt: "Access denied - the information you have entered is incorrect. Please try again".
-
For the attempt prior to the last retry (number of retries limit is set per database): "Warning: Next invalid login attempt will lock the account".
This new feature has been posted as an Idea: Looping in attempt message misleading on Preceda Community and has successfully made it into Preceda V15.8.03. To access the links, make sure you are logged in to Preceda Community. |
68164
As mentioned in a recent Customer Forum, your current investment with Preceda is protected, as Preceda will continue to be developed and enhanced. At the same time, you would have the chance to extend to Dayforce for additional business capabilities (e.g. innovative HCM, Workforce Management, advanced HR Analytics, as well as a harmonized employee experience).
We are happy to update you the integration development in progress. Items added to / updated in Preceda in V15.8.03 are:
-
Dayforce Configuration Mapper (M001820)
-
Dayforce Configuration Extractor
-
Dayforce File Submission Extractor
-
Dayforce Configuration screen
-
Dayforce File Submission screen
If you are interested in learning more about this integration for your organisation, please reach out to your Account Executive.
Payroll
69115
Preceda now supports the download and email of multiple Pay Slips as well as the capability to email Pay Slips to multiple recipients in one go. The Earning History screen and ESS Pay Slip screen have been updated.
There are three possible actions that can now be done to the Pay Slips via the Earning History screen and ESS Pay Slip screen - View, Download, and Email. A new checkbox Select All (X) Pay Slip(s) is available to allow selecting all Pay Slips from the browselist. To shortlist the Pay Slips to be downloaded or emailed, you may want to utilize the Filter icon to specify the selection criteria, or simply hold Ctrl or Shift while you click the mouse.
View Pay Slips
The View button ( ) will be enabled when some Pay Slips are selected from the browselist and the Select All (X) Pay Slip(s) checkbox is unticked. Clicking the button will open the Pay Slips in PDF format, each in separate tabs.
Download Pay Slips
The Download button ( ) will be enabled when either some Pay Slips are selected from the browselist or the Select All (X) Pay Slip(s) checkbox is ticked. When only one pay slip is selected, clicking the button will also only download one PDF file, while when multiple pay slips are selected, a zip file containing all the pay slips in PDF will be downloaded.
Email Pay Slips
The Email button ( ) will be enabled when either some Pay Slips are selected from the browselist or the Select All (X) Pay Slip(s) checkbox is ticked. When the button is clicked, the Email Pay Slip drilldown will open to allow more than one (1) email addresses to be provided.
Encryption to emailed Pay Slips has not been changed. If encryption is turned on in the database, the recipients of emailed Pay Slips would continue to need password to decrypt each Pay Slip PDF. It is thus recommended that users to download Pay Slips and enclose them into an email, if they wish to send them to entrusted third parties.
This new feature has been posted as Ideas Preceda Community and has successfully made it into Preceda V15.8.03. To access the links, make sure you are logged in to Preceda Community. |
70820, 70821
To comply with ATO latest directives, the option Share Scheme Type - P (ESS interest acquired pre-1 July 2009) has been re-enabled for Scheme Type field via the Employee Share Scheme Statement History screen drilldown.
When Type P is selected all ATO fields will be disabled with zero (0) as value, except for the Number of ESS - Taxing Point where the user can input their desired value.
Additionally, when the Type P is selected and the Financial Year input value is 2019 and before, the Discount on ESS Interests field will be enabled where the user can input their desired value. For Financial Year 2020 and after, the field will be disabled with zero (0) as value.
Note that these changes are applied to the mapper accordingly.
System Management
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
69699
Hours Type Code of Classification = R or RDO is now handled correctly whether entered via Entry via Single Screen or imported via Mapper M000471.
69178
Multiple company transfers on the same day via Mapper M001428 now handles the Termination Date correctly. You can now successfully perform multiple transfers via Mapper M001428 where the Termination Date no longer comes before the Transfer Date, and if there is no Transfer Date, the Termination Date is not set earlier than the Hire Date.
Framework
69242
Mapper M000051 no longer rejects the import of a Step From Salary or Step To Salary code value that is greater than four (4) characters in length as it now successfully accepts Step From Salary or Step To Salary values of up to 10 characters.
70344
The Distribute Spoolfile on Preceda Console now correctly displays all the Output Files. Likewise, the Add Filter button is now enabled and the Distribution button is working properly for imported and saved distribution definition.
To all impacted customers:
Kindly follow below steps and check if the issue has been fixed on your end:
-
Go to Console > Spoofiles, then select the File you want to distribute.
-
Click Distribute to open the Distribute Spoolfile window.
-
Click Tools > Export Distribution Definition to get the current distribution list that is corrupted, then save it somewhere.
-
Click Tools > Import Distribution Definition and select the file that has been saved just now.
-
Click OK to the message: Imported package file contains duplicate in FNAME property of filter file. It has now been fixed and should be saved to keep it permanently.
-
Check if it fixes the issues.
To save the auto-fixed distribution list and replace the corrupted one, you may further:
-
Click Save As.
-
Select the original Distribution Name.
-
Click OK.
59028
Bank Details Mapper M000656 will now correctly update Net Bank file when delete action (Action = D) is used to end a Bank Split early.
70342
The Payrun Message screen has now been fixed so that no error will be encountered when there are more than 9,999 records available.
70112
The user session will no longer be affected when searching on Organization > Position > Associate groups/ Certifications with Position screen.
Payroll
60219
Pay Enquiry for each Pay Separator on Entry via Single Screen now displays the correct description for A/D TAX/ADJ. The description of A/D Code added on a standard pay slip is no longer being copied over to the additional pay separator's A/D Code description.
66115
The Express Pay Report will now show the correct Company Totals per Cost Level 1 when Express Pay transactions with zero (0) dollars to the Net Bank account exist.
69222
The processing of Costing Splits has been fixed and will be applied as expected for transactions generated by Express Payment.
69431
EFT Group deductions will now correctly and consistently display in Bank Credit reports (PAY65, PAY68) and PAY64 report.
54660
The EFT Processing Report - EFT Consolidated Negative/ Zero Amounts is now showing the correct employee details.
70406
No error message will now appear after running Retro Pay when more than 100 messages exist per one employee. Payrun calculations will now successfully proceed as expected.
58855
Retro is now correctly calculating where retro over termination payment includes overtime.
70949
Employer Level 1 and Level 2 descriptions with special characters, entered via Employer Information screen, can now be reported through STP. Any invalid character value written in the STP xml file will now be parsed and be replaced with a space so that submission to ATO will not fail.
69316
Leave entitlements are now correctly updating for a terminated employee whose termination process was executed via the Express Payments - Termination wizard and passed to the Time Card Entry. Additionally, the employee's Leave History will now reflect correct values upon closing the corresponding Payrun.
Remuneration
69200
The Contract Paid Amount is now getting cleared (i.e. set to zero) when saving a new package or inserting a current A/D record which Effective Date is after Paid Up to Date.
Version 15.8.02
Enhancements
Administration
69345
The Calculate Leave Accrual process has been enhanced to accrue leave for Work Hours-based payments made in off-cycle payruns. This update identifies and processes all employees who are paid based on Worked Hours and paid through an Off Cycle Payrun, regardless if leave accruals have already been completed for the same period end date in the previous Payrun (i.e. calculate leave accruals for all payment made in off-cycle Payrun).
To improve the accuracy of leave accrual process, the system has been changed from using Earning History files (PEPWAD, PEPWEH) to the Timecard Cost History file (TCOSTH) as a source of information for Work Hours base Leave Accruals.
67169
A hover over comment feature has been added to the Review Leave Application. This enables Managers to quickly review leave comments on the leave browselist without needing to drill down on the details screen. This hover over comment feature increases the overall user experience and awareness of valuable information for manager approval, thus supports rapid decision-making.
The comment icon is available on the Review Leave Application screen if a comment exists in the leave request. If there is no comment for a leave request, the icon on the screen is hidden. Hovering over this icon on the browselist will display the actual comment of the leave request (i.e. to show up to 252 characters).
61827
A new screen validation has been added to Leave Accrual Method screen for Anniversary Branch. This new validation identifies whether the leave accrual methods are correctly configured with Anniversary Branch against the Period No. This validation ensures that the:
-
Anniversary Branch must not be equal to the Period No;
-
User is informed of the action to take (i.e. update the Period No).
The same validation has been applied in the corresponding Mapper (M000041) and Leave Calculation program, ensuring that incorrectly configured data are skipped. If a given customer database has incorrect combination of data recorded for Anniversary Branch and Period No, the Leave Calculation program skips the incorrect records and outputs a validation message to the exception report. Similarly, if any incorrect combination of data (Anniversary Branch vs Period No) has been imported using the corresponding Mapper, a validation message will be made available in the mapper report.
69584
The entries on Leave History screen are now by default sorted from the latest Leave Start Date. This saves you effort to sort them by date every time you come to this screen.
This new feature has been posted as an Idea: Leave History screen should auto sort by date not leave type on Preceda Community and has successfully made it into Preceda V15.8.02. To access the links, make sure you are logged in to Preceda Community. |
Payroll
47177
To ensure payments for leave are processed correctly for customers who have configured Hours Type Codes with Pay by Units = Y, avoiding incorrect payments, the validation on the saving of records on Entry via Single Screen has been updated.
This ensures that:
-
Hours Codes with Pay by Units enabled can only be used when employees' Leave Entitlements are stored in the same Unit type (Weekly, Daily). Warnings will be provided, and transactions will be dropped as required.
-
Hours Codes with Pay by Units enabled will always perform payment calculations using Leave Units. The Calculate Payrun has been updated accordingly. Warnings will be provided if no Leave Units value is provided, and transactions will be dropped as required.
-
Calculation Methods using Unit Rates cannot be used with Hours Codes that use Hourly Rates in the payment calculations.
When the payment is based on Hourly rates (i.e. Pay by Units = N) and the employee has a Daily/Weekly based Calculation Method, to ensure that only Calculation Methods using Hourly rates are included in the payment calculation, Calculation Method overrides will be ignored and excluded from the payment calculation logic. A warning message will be presented advising of the suppressed override.
These warning messages have been added on the Entry via Single Screen to advise users of the corrections required to prevent transactions from being dropped when processing payrun. These error messages have also been made available on Retro Entry via Single Screen and the Detail Entry screen of Express Pay Wizard (i.e. displayed only when moving Back to return to Detail Entry).
When the Time Card Print process is run and there are still transactions identified as being invalid, they will be dropped so that they are excluded from the calculated payment results. When these transactions are dropped, they will be reported on the TCHAD Timecard Hours, Additions and Deductions Report, with messages also output to the Payrun Messages screen. The Payrun Dashboard's count of the number of messages for the Group and Severity information recorded against each message will also be updated.
-
Invalid Hours Type Code for Employee - Leave transactions for Classifications which require a Leave Entitlement to exist, a check will be performed upon save on EvSS for Hours Type Codes with Pay by Units = Y. This ensures that the employee has a Leave Entitlement record set with the required Unit Type. This applies to Hours Codes of Classifications L, S, or V, and for Classification O where the Accrual Classification Type is populated with a value. Where the employee's Leave Entitlement record is setup with a different Unit Type to what is configured against the Hours Code, a warning message will be presented.
-
Leave Hours Type with no Leave Units - A warning message will be presented upon save on EvSS where an Hours Code has Pay by Units = Y, there is no associated Leave Entitlements (PEPACC) record on the employee and no Leave Units value has been provided.
New System Health Checks
To highlight any records with incorrect configuration, new items specific to the Pay by Units functionality have been added on the System Health Check screen's Hours Type Code Configuration and Payment Details - Current Employees.
63066
The Source of Change associated to Hours and A/D transactions in Timecard Cost History (TCOSTH File) has been updated to include specific information for records imported into the Payrun, to easily differentiate these from any manually entered records. The new Source of Change identifiers include MAPPER, ESS, and PAY43T. This information can be reported over in Extractor via Administration > Earnings > Timecard Cost History.
Below is a table to represent the primary sources you may see and their corresponding sources:
Source |
Extractor: Timecard Cost History Field Name: Source of Change |
---|---|
Manual data entry | TIME CARDS |
Import via Mapper M000471 Inbound Integration - M000471 T/A Import - M000471 |
MAPPER |
Import Self Service Transactions to Payroll | ESS |
T/A Import - PAY34T (in non-TIME database) T/A Import - PAY34T (in TIME database) |
PAY34T TIME |
Export to Payroll | TIME |
Release Retro transactions | RETRO PAYP |
Time
60383
The Selection Criteria screen, commonly used in TIME processes, has been enhanced enabling the selection of up to 10 Pay Period Rules. This will save you effort in running the process more than once just to accommodate employees associated with different Pay Period Rules. This update applies to all screens containing the Selection Criteria such as:
Absentee Report | Headcount Report | Time Cards Report |
Absentee History Report | On Premises Report | Time Card History Report |
Annualised Salary Reconciliation Calculation Wizard | Pay Period Recalculation | Time Monitor Report |
Annualised Salary Reconciliation Payment Wizard | Post Times | Time Monitor Update |
Budget vs Actual Report | Post Times - No Roll | Total Hours History Report |
Budget vs Actual History Report | Pre Post Time Report | Total Hours Report |
Consecutive Days Off Report | Primary Roster Export | Unachieved Shift Break Report |
Coverage Report | Punch Detail History Report | Wage Analysis History Report |
Create Bulk Entry of Time | Punch Detail Report Selection | Wage Analysis Report |
Employee Master Report | Reverse Posted Times | Weekly Roster Report |
Expanded Labour Analysis History Report | Rostered Not Clocked In Report | Weekly Transfer Roster Report |
Expanded Labour Analysis Report | Split Shift Report | Work Pattern Roster Copy |
66649
A Date / Time (To) field has been added on the Annualised Salary Reconciliation Calculation Wizard > Selection Criteria screen. This is introduced to address the need of reconciling an employee up to a Period End that is different from their latest Period End. This could be most relevant when employees have been moved off from an Annualised Salary clause but reconciliation was missed before further payruns are closed.
-
The Date / Time (To) is editable and optional. When left blank, the process will reconcile employees up to their latest Period End on or before their Due Date.
-
When a To Date value has been provided, the processing will run on the date range from the employee's Annualised Salary Review Start Date, reconciling up to the latest Period End Date on or prior to an earlier value between these two:
-
Employee's Reconciliation Due Date -1; or
-
The To Date specified.
-
The calculated result will be passed on to the Payment Wizard for further processing as it happens now. This option is only relevant when you run the Annualised Salary Reconciliation Calculation Wizard manually (i.e. the reports auto-generated upon Payrun Close are not affected by the setups here).
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
67854
Updating an employee's Base Hours (e.g. from 38hrs/week to 22.4hrs/week) will trigger an update to the Employee FTE Hours Per Week and FTE Hours per Week. This would happen when the Program Control FTE Full Time Equivalents Positions 14 and 16 have been configured to Y and O, respectively:
-
Calculate FTE - Calculation of Employee FTE will be performed by the system and the Employee FTE field is read-only.
-
Override the value for Employee FTE Hours per Week with Employee Base Hours.
69197
The Gender field on the Personal screen now correctly uses and displays the Code in the input field instead of the Description.
Payroll
68565
Entering a value of '99999.9999' as rate for an A/D on the Entry via Single Screen now correctly displays '0.00' on the Time Card Entry Report, properly considering it as an override of zero instead of rounding the value.
67788
The calculation in Express Pay Wizard and Termination Wizard now includes the correct calculation of the Allowance/Deduction rates, which is equivalent to difference between Contract Amount and Contract Paid Amount.
67113
Self Service Transactions from payroll are now successfully cleared when resetting payrun and canceling leave, ensuring that the cancelled leave is not included in the employee payment.
58936
When using the Bulk Pay slip Options Update, only the selected employees (i.e. submitted for a specific Company for a specific Pay slip Type and Pay slip Delivery Method) are now correctly being updated and reflected in the report. This no longer includes all employees, unless specified, and properly referencing the Selection Criteria for an accurate reporting.
69106
The Company Bank Account Number being generated for the ASB Bank File format is now correct and has leading zeroes as it is no longer being converted into a numeric field so that all characters are referenced and retained.
68582
The extra records which Preceda issues is no longer double calculated when updating Gross, Tax, & Net, regardless of deductions or allowances so that the balancing record will still remain, and no out of balance occurs on the Payroll File Master Control Report (PAY12PRT).
60640
The prorated Worked Hours are now rounded correctly before and after having Effective Date changes, (i.e. when generating retro with an effective dated costing change).
66825
The Pay Rate for Position 23 is now picked up successfully when referenced in Hours Type Codes and elsewhere, confirming the proper pay rate being retrieved for the correct overtime calculation and payment.
66811
LSL accruals are now accruing correctly (i.e. when using Unit Type = Weeks or run Fortnightly). The leave accrual value is properly being rounded off to five decimal places before getting truncated.
Remuneration
67886
The Salary Review and import process have been fixed so that the Gross for Super Package Components are now correct when implementing a change via Import Salary Review.
Reporting Tools
69116
You can now run the package successfully without any error message occurring on Console > Distribute - Spoolfiles, after the package is selected and distribution is run/modified.
69220
You can now successfully create a Report Manager Package with Extract Task that has Run Time Parameters without any issues.
System Management
69409
Only employees who are reported in the current Financial Year via STP or PSAR are now included in the Year End Reconciliation process, avoiding any error and no longer holding up the integration. Any employees terminated with zero YTD figures and with all E018 flags set to blank no longer appears on the PSAR report.
Version 15.8.01
Enhancements
Administration
65930
The Australian and New Zealand governments have recently announced the new gender standards for 2021, stating the variables that should be used when collecting gender information.
As part of Ceridian's commitment to Diversity, Equity and Inclusion, as well as for compliance, the gender variables to be used in Preceda is updated to match the latest guidelines.
The new gender descriptions and code available are as follows:
Australia (AU)
* Reference: ABS - Standard for Sex, Gender, Variations of Sex Characteristics and Sexual Orientation Variables, 2020
Gender Descriptions | Code |
---|---|
Male | M |
Female | F |
Non-binary | X |
Different Term | T |
Prefer not to answer | Z |
New Zealand (NZ)
* Reference: StatsNZ - Statistical standard for gender, sex, and variations of sex characteristics, 2021
Gender Descriptions | Code |
---|---|
Male | M |
Female | F |
Non-binary | X |
Different Term | T |
Prefer not to answer | Z |
Screens Update
Two (2) new fields, namely Preferred Gender Identity and Preferred Pronouns, are added to the following relevant Preceda screens where gender is often maintained:
-
Dependants (only Preferred Gender Identity field is added)
-
My Details (Preceda Mobile)
Below describes the newly added fields:
-
Preferred Gender Identity - this field will only be visible and editable when the user's chosen Gender is Different Term (T) for AU/ Another Gender (T) for NZ.
-
Preferred Pronouns - this is an optional field. Gender pronouns are the terms people choose to refer to themselves that reflect their gender identify (i.e., he/him, she/her, they/them). If provided with a value, it will reflect on the Business Card in Notifications and via Entry Via Single Screen (EvSS).
Extractor Updates
The corresponding extractors of the relevant Preceda screens were also updated to include the new fields.
Additionally, in the Dependants extractor, the first Gender label field has been renamed to Gender Desc.
Mappers Updates
The following Mappers have been updated to add the new fields with their respective validations:
-
Hire Mapper (M999777, M999777BK, M999777NZ, M999777NZBK)
-
Personal Details Mapper (M000211, M000211NZ)
-
Dependants Mapper (M000114)
-
Applicant Register (M000172) - for this mapper, the Create access right was removed
Notably, the 2 new fields are optional, so they will not affect the existing mapper templates.
Reports Updates
These reports display a breakdown of Gender and has been updated to include all new gender options:
-
Reconciliation Payrun Group
-
PTD Reconciliation
-
YTD Figures - Active Employees
-
YTD Figures - All Employees
-
Personnel History Record
This new feature has been posted as Ideas (see below list of Ideas with links) on Preceda Community and has successfully made it into Preceda V15.8.01. To access the links, make sure you are logged in to Preceda Community. |
Integration
67141
With the acquisition of Ascender by Ceridian we now have an integration between Preceda and Dayforce, Ceridian's flagship HCM Product so you can take advantage of both Ceridian offerings.
The integrated experience is as follows:
-
The Payroll Experience - Preceda will continue to be used for payroll processing. All the payroll processing features currently being used, e.g. One Step Processes, Health Checks, Payroll Dashboard, will still be available in Preceda to help you effectively run your pay.
-
The Employee, Manager and HR Experience - Dayforce can be used for combining the Employee and Manager experience into one interface. It can include everything from leave applications and approvals, time sheets, HR functions and more. From the HR Admin perspective, this covers the entire cycle from recruitment to succession planning.
The information from the key activities conducted in Dayforce will flow into Preceda, as required for payroll processing, thereby creating a one-stop shop integrated solution for all HR and Payroll needs between the two interfaces.
Below is the list of some key offerings available in the Dayforce and Preceda:
If you are interested in learning more about this integration for your organisation, please reach out to your Account Executive.
Payroll
66603
The Company Bank Details screen has now been updated to support multiple bank file formats for customers in Australia and New Zealand. This change introduces a Bank File Format field used to identify the unique banking requirements for each Company and Payrun Group combination. The file formats available will include the existing global bank formats as well as the standard ABA file for Australia, and some of the existing formats available via Program Control PAY64 for New Zealand. All references to Preceda Variable *PP_BANK_FILE_METHOD have new been removed, allowing for local bank formats and global bank formats to both be available to customers in the same database.
Other specific changes to the Company Bank Details screen that has been implemented are the following:
-
The Payrun Group field and the Bank Files Format field (previously Company Bank File Output Code) are moved to the top of the screen.
-
Quick Search and Advanced Searchnow include searching by Payrun Group.
-
New options are added to the Bank File Format field:
-
For AU, the ABA option has been added for the Australian ABA File; a separate Group Box for all ABA fields is now available, only requiring these fields to be updated when using this format:
-
For NZ, the PAY64 option has been added, which refers to the existing Program Control PAY64 to identify the required file format; All ABA specific fields have been removed from the NZ screen.
-
-
The Company Bank Account Information Group Box has been introduced, with some field labels updated:
-
Company BSB Number (for AU) / Company Bank Key (for NZ) field is now changed to BSB Number
-
Company Bank Number is now changed to Account Number
-
-
The Additional Bank File Information Group Box has been introduced, with some field labels updated:
-
All Additional Bank Details fields have been changed to simply Additional Details (i.e, Additional Details 1)
-
Description of Entries is now changed to Additional Details 3
-
Moreover, in the EFT Processing screen for AU, the Bank Type field is now only visible and relevant when the selected Bank File Format = ABA. While for NZ, the field is removed and no longer available.
3288
New Zealand has many bank file formats required by each of the different banks operating in this country. Some employers have accounts with multiple banks and as the bank file format varies depending on which group of employees are being paid, there is a need for them to have control over which formats are required for each employee. The existing method allows for only one (1) bank file format per database to be set up via Program Control PAY64.
To support customers with multiple banks, the ability to configure multiple formats at the same time has been implemented. A number of the NZ bank formats available under Program Control PAY64 have now been developed into individual program options, that can be selected from the Bank File Format field on the Company Bank Details screen.
This will provide more control over which bank files are required for each company in the database.
This enhancement only covers the creation of new options for ASB Bank, Bank of New Zealand, ANZ Bank and the ANZ Domestic bank file formats. The remaining formats for other local banks will be catered for in a later enhancement.
As this will be a gradual transition and migration to the new method for identifying which format is required, the existing method is still maintained and can be used for all bank file formats supported via Program Control PAY64.
The new method will also generate a report which includes New Zealand specific information for employee Code, Particulars, and Reference information.
The new programs for the ASB Bank, Bank of New Zealand, ANZ Bank and the ANZ Domestic will generate bank files in the same format currently generated via Program Control PAY64 with few minor differences.
Below is a summary of the changes implemented for the bank file formats:
Bank | Bank File Format | Expected Preceda Values |
---|---|---|
ASB Bank | The format of the ASB Bank file is a fixed position flat file, with each field of information represented by a set number of positions within each record. |
When Bank File Format = ASB, it generates first 20 characters of "Account Name" from the Company Bank Details record
When Bank File Format = PAY64, it generates the first 16 characters of "Account Name" from the Company Bank Details record, followed by 4 spaces |
Bank of New Zealand (BNZ) | The file contents are formatted like a CSV file with the comma character separating each field, but the file is generated with a .TXT extension. |
When Bank File Format = BNZ, the fixed value is "52"
When Bank File Format = PAY64, the fixed value is "50"
When Bank File Format = BNZ, it generates the first 20 characters of "Account Name" from the Company Bank Detailsrecord
When Bank File Format = PAY64, it generates the first 16 characters of "Account Name" from the Company Bank Details record |
ANZ | The file contents are formatted like a CSV file with the comma character separating each field, but the file is generated with a .TXT extension. |
When Bank File Format = ANZ, Date the file was created in CCYYMMDD format
When Bank File Format = PAY64, "Direct Credit Date" from EFT Processing in CCYYMMDD format
When Bank File Format = ANZ, it populates the first 20 characters of "Account Name" from the Company Bank Details record
When Bank File Format = PAY64, it populates the first 16 characters of "Account Name" from the Company Bank Details record |
60298
The New Zealand Inland Revenue Department (IRD) has announced tax changes for Financial Year 2022-2023. Below are the changes implemented:
ACC Earner Premium Threshold and Rates
From the first Pay Period ending on or after the 1st of April 2022:
-
The maximum income to which the ACC Earner Premium Rate applies increases from $130,911 to $136,544.
-
The Earner Premium Levy is also being updated from 1.39% to 1.46%.
Student Loan Threshold
Effective from 1st of April 2022 the student loan repayment threshold increases to $21,268 for the 2022/23 tax year. This is an increase from $20,280 per year / $390 per week to $21,268 per year / $409 per week.
The Tax Table Update Button will be available on the Preceda Welcome Page from March 14, 2022.
Note that only users who have Administrator and Security Officer set to “Y” in Define Users screen will be able to see the message on the Welcome Page and click on the button.
Organisational Management
64825
The 'Use this level' concept has now been introduced to the Costing Defaults. It is a checkbox on the screen and a Y/N via mapper (M000087). It enables the flexibility at each Cost Level to determine whether an employee's existing Cost Level information should be affected at all if Costing Defaults is applied in a position change.
There can be three (3) combinations to a Cost Level when defining a Costing Defaults. Below explains what each combination means to an employee in their position change:
Use this level | Cost Level | When Costing Defaults is used in Position Change |
---|---|---|
Ticked / Y | With value | Use this value |
Ticked / Y | Blank | Clear out existing if any |
Unticked / N | Blank | Retain existing if any |
Example:
Use this level | Cost Level | Example | When Costing Defaults is used in Position Change |
---|---|---|---|
Ticked / Y | With value |
State Cost Centre |
Result: SA Result: LJTRAVEL |
Ticked / Y | Blank | Account Department |
Result: blank Result: blank |
Unticked / N | Blank | Location Wage Groups |
Result: retained existing Result: retained existing |
The 'Use this level' flag is not relevant to Cost Level 1, because this Cost Level 1 is not affected by position change anyway. Similarly, it is not relevant to Job Title either.
All existing Costing Defaults will be updated as below:
Cost Level (in 15.8.00) | Use this Level (in 15.8.01) | Cost Level (in 15.8.01) |
---|---|---|
With value | Ticked / Y | With value |
Blank | Unticked / N | Blank |
Adjustments might be needed before you apply them to the next position change.
Mapper and Extractor Updates
A new mapper (M000087) for Costing Defaults has been introduced.
Extractor is updated accordingly to include the new 'Level x Used' fields.
This new feature has been posted as an Idea: Add Mapper for Costing Defaults M000087 on Preceda Community and has successfully made it into Preceda V15.8.01. To access the links, make sure you are logged in to Preceda Community. |
System Management
64389
With the Ceridian acquisition of Ascender, Preceda Desktop and Mobile's look and feel has now been updated to the Ceridian branding and theme.
Preceda Desktop Logon page:
-
The new log in experience applies to ALL Users.
-
The new experience after log in takes effect automatically ONLY for users:
-
Not using customised themes;
-
Not associated with Group Profiles; OR
-
Who are associated with Group Profiles,
-
AND Group Profile -> Theme Name = blank
-
OR Group Profile -> Theme Name = PRECEDA ASCENDER (in 15.8.00).
-
-
-
Users who are associated with Group Profiles AND Group Profile -> Theme Name in below image will notice the Company Logo being changed to Ceridian Preceda.
Preceda Desktop's new Default look (i.e. updated menu background colour, new Ceridian Preceda logo, blue and grey theme):
Preceda Mobile colours and logo have also been updated to Ceridian Preceda.
Preceda's Online Help, the Knowledge Base (KB), has also been rebranded to the Ceridian look and feel.
-
Please note that the KB Toolbars are now within the KB Page's content section, and all are left aligned.
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
61635
Company Transfer is updated to handle bulk transfers that involve changes in more than 1 level, e.g. Cost Level 1 + Payrun Group.
65101
Bank Details Mapper M000656A will no longer create orphaned or incomplete Net Pay bank details for employees who have not yet been hired in Preceda.
63080
Bank Details Mappers M000656* will be processed normally even if no employee in the database has any Allow/Deduct records - usually the case when implementing a new database.
68242
Saving changes in Classification screen no longer produces an error message. Changes are now saved successfully.
Framework
64510
When using the Google Chrome browser, resizing the drilldown windows of Position Structure and Position Occupants in Org Units screen (M001646) no longer produces any Yikes or script error.
Payroll
68660
ETP Tax calculation is now corrected to ensure that when working out the concession/non-concession part in an ETP payment, OTP payment is reduced from the whole-of-income cap.
63516
Tax calculations from the Termination Wizard are now correctly passed to the payrun when transactions from Entry via Single Screen including results from Retro Pay were imported into the Termination Wizard.
68714
Leave Reason records are now generated as expected for terminated employees, as well as for active employees that will not be paid again in the financial year.
63528
Occupants Report process is updated to complete normally even if no employee would be found in the specified date range.
60652
Retro Pay now generates results as expected, even when changes have been made to other employee standard A/D records that are not flagged for inclusion in the Retro Pay calculations.
61124
The Tax Weeks Override value is now referenced and displayed correctly in Tax Weeks Used in Calculated Payment drilldown when Post Data from Time checkbox is ticked in Express Pay and Termination Wizard.
68370
The Total Tax column in PAYG Tax Report now displays the correct value each Period End Date.
Time
59966
When hour and minutes is chosen for Elapsed Time Format on the Time Configuration screen, the Total Distribution of Hours is now correctly calculated upon save. It is now correctly reflected against the values displayed in the drilldown of Time Editor > Total Hours to be Distributed.
58705
Some punches for a few employees were loading as read-only preventing it to be approved or edited. This has now been fixed to ensure that punches in Time Editor are not being greyed out when user inserts a punch via Insert Punch button on Time Editor Screen and importing Transactions.csv file using Preceda Connector.
Version 15.8.00
Enhancements
Administration
64530
To assist customers and the support team with investigating issues related to an employee's leave balance and calculations within G/L Leave Liability Movement, changes made in the Employee Leave Entitlements (PEPACC) file, via the following actions, are now captured in the Employee Audit Log (A001):
-
Updates to the Leave Entitlements via screen
-
Updates to Leave Entitlements via Mapper M000657
-
New Hire via Hire Wizard with Leave Entitlements added manually
-
New Hire via Hire Wizard with Leave Entitlements added via Position via Leave Defaults
-
New Hire via Hire Mappers (M999777, M999777BK, M999777NZ, M999777NZBK, M999777PH, M999777PHBK) with Leave Entitlements added via Position with Leave Defaults
-
Position change to a Position with Leave Defaults via screen
-
Position change to a Position with Leave Defaults via Mapper M000222E
Note, however, changes made to the Leave Entitlements via the following actions will NOT be captured in the Employee Audit Log (A001):
64220
The Issued Date and Expiry Date fields on both Passport Details and Lic/Reg Summary screens have been updated to allow users to input the correct year using the dd/MM/yyyy (i.e. 01/01/2035) format instead of the previous dd/MM/yy (i.e. 01/01/35) format.
Framework
60374
The Print Preview option is now made available for more Preceda screens and drilldowns. If the feature is not in the menu bar, access it via Tools > Print Preview.
A few screens you may feel interested in:
-
Time Editor (T000002)
-
Review Retro Pay (M001692)
-
Retro Entry via Single Screen (M001737)
-
Annualised Salary Reconciliation Payment > Calculation Options (T000216)
-
Annualised Salary Reconciliation Payment > Review Calculation Selected (T000217)
66185
Preceda is updated to support running Crystal Report on non-ActiveX browsers. This means browsers other than IE can also be used to run Extractor Crystal Report.
In non-ActiveX browsers, Extractor has been updated to cater for this:
In non-ActiveX browsers, Console has also been updated to allow downloading Crystal format datafiles. If such a file is available, you may download it by clicking the View button.
61899
The Release Express Payments extractor is updated to report over the values calculated in the Wizard.
New fields added: Hours Value, A/D Value.
Existing fields relabeled: Leave Unit to Leave Units, A/D Unit to A/D Units.
Some fields are repositioned.
Organisational Management
66009
The Payroll Defaults screen has been updated for all countries to improve user experience by grouping relevant fields to group boxes.
Meanwhile, a new field STP Employment Basis is added to both the Payroll Defaults screen and the Mapper Hire Defaults screen for Australia. This is to assist with capturing information for Single Touch Payroll (STP) Phase 2 reporting.
A new field Employment Status is added to the same screens for Philippines.
This new feature has been posted as an Idea on Preceda Community and has successfully made it into Preceda V15.8.00 To access the links, make sure you are logged in to Preceda Community. |
Corrective Maintenance
The following Defects have now been addressed and resolved successfully.
Administration
67375
Certifications Obtained screen has been updated to display employee's certifications only once.
If an employee has been associated with the same Certification in multiple ways (e.g. via two or more Positions or Groups) a tooltip will appear in the newly introduced Associations column to indicate this.
65435
Termination processes have been updated to ensure that Change Reasons on employee's salary, payment details, etc. are retained after termination.
64593
When the Leave Accrued To Date is in the future, the Today's date was not used as a basis when retrieving the Pay Rates for use in General Ledger Leave Liability Movement, thus the calculations were incorrect. This has now been fixed to ensure that the current rates of Today's date for the General Ledger Leave Liability Movement calculations is used accordingly when either Position 27 or Position 28 is set to T in Program Control LVACC.
67533
Applying for leave via My Leave and Leave by Proxy will no longer freeze when the Hours Away or Public Holiday Hours Away is greater than the scheduled working hours.
Framework
63298
In the Report Manager, the newly added and saved subscriber is now retained and displays the correct details upon reopening. When the newly added subscriber is searched, the correct details will also be displayed.
62577
When extracting Security Profiles in the Extractor, the generated report will now contain the correct data using the selected/saved preferences.
62040
Preceda Mobile has been updated to allow entering the decimal separator or dot (.) in iOS devices. This update has been implemented when entering hours on the following:
-
Hours Away and Public Holiday hours away fields on My Leave screen
-
Hours field on My Time
62741
Due to large spool file creation, a Message Wait occurred for some of Report Generating Programs when processed. This has now been fixed by increasing the limit size for spool creation to a maximum record of 2000000 for the following reports:
-
G/L Posting PDT File Report
-
Retrospective Pay Report
-
Maintenance Audit Report
-
Bulk Pay slip Options Update
54410
In the Report Manager, submitted single run scheduled jobs or packages can now be deleted via Preceda Console under Extract Jobs.
64717
Using Change Base Hours wizard creates data anomalies to employee's payment details information, e.g. Base Hours, Auto Pay, Work Pattern, etc. For this reason, the Change Base Hours wizard, including the Contract Hours Leave Types and Contract Hours History screens, will now be retired from Preceda. To change Base Hours Code, please utilitse the Payment Details screen. Note that the Contract Hours History Extractor can still be viewed on Extractor Window. Any uncatered requirements due to this change will be considered in upcoming NZ enhancements.
Payroll
65453
Making an amendment on a terminated employee in a previous financial year will no longer trigger that employee to be included in the current financial year STP Pay Event Reporting.
65954
There was a specific scenario where employee’s Status is cleared after resetting payrun. Correction is made to ensure employee’s Status will no longer be cleared unexpectedly.
60194
The updated Pay Frequency will now be correctly reflected in the Gross Pay Report and Gross Pay Report with Variances for employees with multiple and/or other versions.
61341
The General Ledger now generates the correct posting transactions, based on the setting of Position 25 of Program Control LVACC, when employee changes Costing Splits without other changes to the Standard Costings; thus, the correct Leave Liability Movement values are now also displayed for employees.
64727
When running a payrun process up to Masterfile Update Complete for Success Factors, the employees' Preceda ID numbers were incomplete as the leading zeroes were dropped in the generated Manifest file. This has now been corrected to ensure that the full Preceda ID numbers are populated in the first column of the Success Factors Manifest file.
67399,67804
The following updates were implemented to the JP Morgan Bank File:
-
Double quotation character (") is now removed from fields 2, 17, 28, 29
-
The extra space at the end of each line is now removed
-
The format of the account number is now correct which is a concatenation of leading zeros, Account Number as on the Bank Details screen, and suffix as on the Bank Details screen
Time
67122
In the Daily Interpreter Rules, when using Source Type Total Hours Worked with a set From and To Time, the Meal Break is incorrectly deducted from the calculation even if the employee did not have any hours during that time. This has now been fixed to ensure that if the Meal Break start time falls outside the time range of the Total Hours Worked rule, no meal break deduction would apply.
65070
When drilling down and making a change in the Individual Primary Rosters screen, the Roll Roster field now retains its new value upon save. It will no longer revert to the default value for the employee.
65068
The Roll Rosters field on Time Details is now corrected and changed to a prompt field instead of a checkbox. The available options for this prompt field are:
-
N - Do not roll any primary roster information forward
-
T - Roll rostered transfers IN ADDITION to the primary
-
Y - Roll ONLY the primary roster forward
64627
The Group Approval screen has been corrected to ensure terminated employees' unposted Prior Period Hours will not affect the calculation of Prior Period Hours for the next active employee.